Update Issue Comment

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate readOnlyHint=false, and the description confirms a mutation ('update'). No contradictions, but the description adds minimal behavioral context beyond what annotations provide, such as auth requirements or side effects.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two concise sentences: one for the core purpose, one for a critical usage note. No redundant or irrelevant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the output schema existence and parameter descriptions, the description covers the main purpose and a key nuance. It could mention error conditions or permissions, but overall it is sufficient for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so parameters are already documented. The description adds value by explaining the 'summonees' parameter's role in mentioning people, which is not fully captured in schema descriptions. At baseline 3, this is adequate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the specific action ('Update an existing comment') and the resource ('Yandex Tracker issue'). It distinguishes from sibling tools like issue_add_comment and issue_delete_comment by focusing on updating an existing comment.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes an important note about using the 'summonees' parameter for notifications, providing partial guidance. However, it lacks explicit instructions on when to choose this tool over alternatives (e.g., when to update vs add/delete) or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.