Skip to content

Improve tool descriptions and fix translation key collision for AI agent guidance - #142

Open
ma1728 wants to merge 3 commits into
nulab:mainfrom
ma1728:improve-tool-descriptions
Open

Improve tool descriptions and fix translation key collision for AI agent guidance#142
ma1728 wants to merge 3 commits into
nulab:mainfrom
ma1728:improve-tool-descriptions

Conversation

@ma1728

@ma1728 ma1728 commented Jul 1, 2026

Copy link
Copy Markdown

Summary

Improves tool description strings so that AI agents (Claude, GPT, etc.) are guided to use the description field in add_issue / update_issue instead of writing primary issue content via add_issue_comment.

Also separates translation keys for parameter-level descriptions to avoid collisions with tool-level descriptions, and provides Japanese translations.

Closes #141

Changes

addIssueComment.ts — Tool-level description

Before: "Adds a comment to an issue"
After: "Adds a supplementary comment to an existing issue. Use this for follow-up notes, status updates, or discussion — not for the primary issue description. To set or update the main issue content, use add_issue or update_issue with the description field instead."

addIssue.tsdescription parameter

  • Introduced new translation key TOOL_ADD_ISSUE_DESCRIPTION_FIELD (previously shared TOOL_ADD_ISSUE_DESCRIPTION with the tool-level description)
  • Before: "Detailed description of the issue"
  • After: "Detailed description of the issue. This is the primary field for explaining the issue context, requirements, and acceptance criteria. Prefer this over adding a comment."

updateIssue.tsdescription parameter

  • Introduced new translation key TOOL_UPDATE_ISSUE_DESCRIPTION_FIELD (previously shared TOOL_UPDATE_ISSUE_DESCRIPTION with the tool-level description)
  • Before: "Detailed description of the issue"
  • After: "Detailed description of the issue. Use this to set or update the main issue content rather than adding a comment."

.backlog-mcp-serverrc.json.example — Japanese translations

  • Updated TOOL_ADD_ISSUE_COMMENT_DESCRIPTION
  • Added TOOL_ADD_ISSUE_DESCRIPTION_FIELD
  • Added TOOL_UPDATE_ISSUE_DESCRIPTION_FIELD

Why separate translation keys?

Previously, TOOL_ADD_ISSUE_DESCRIPTION was used for both the tool-level description ("Creates a new issue...") and the parameter description ("Detailed description of the issue"). When a user set a Japanese translation for this key, both contexts received the same string — which made no sense for the parameter. The new *_FIELD keys resolve this.

Testing

All 396 tests pass (pnpm test).

前田 省悟 added 2 commits July 1, 2026 17:15
… field

- Clarify add_issue_comment is for supplementary comments, not primary content
- Enhance description field hints in add_issue and update_issue
- Help AI agents prefer the description field over adding comments

Closes nulab#141
…slations

- Introduce TOOL_ADD_ISSUE_DESCRIPTION_FIELD and TOOL_UPDATE_ISSUE_DESCRIPTION_FIELD
  to avoid key collision with tool-level descriptions
- Update .backlog-mcp-serverrc.json.example with Japanese translations
- Ensure the improvement works for Japanese users using translation config
@ma1728 ma1728 changed the title Improve tool descriptions to guide AI agents toward description field Improve tool descriptions and fix translation key collision for AI agent guidance Jul 1, 2026
@katayama8000

katayama8000 commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

@ma1728
Thanks for the proposal!

The wording changes I'd like to hold off on. Not everyone uses Backlog the way your team does.
And You can override descriptions. https://github.com/nulab/backlog-mcp-server#i18n--overriding-descriptions
That's why I'd like to keep the defaults neutral.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Improvement] Improve tool descriptions and fix translation key collision to guide AI agents properly

2 participants