Update Issue Comment

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

The description adds minimal behavioral context beyond the annotation (readOnlyHint: false). It does not disclose side effects, required permissions, or reversibility. The only extra hint is about the summonees parameter, which pertains to parameter usage rather than behavior.

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?

The description is extremely concise with two sentences. The purpose is front-loaded, and the important usage note is placed immediately after. Every sentence earns its place with no redundant 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 presence of a complete output schema and 100% schema coverage, the description is fairly complete. It mentions the key usage hint for notifications. However, it could briefly mention when to use this tool versus other comment-related tools for better completeness.

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?

The input schema has 100% parameter coverage, so the baseline is 3. The description's note about the `summonees` parameter adds slight value but does not substantially enhance understanding beyond what the schema already provides.

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 'Update an existing comment in a Yandex Tracker issue' with a specific verb and resource. It distinguishes from sibling tools like issue_add_comment and issue_delete_comment, leaving no ambiguity.

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 provides an important note about using the `summonees` parameter for notifications, which is helpful. However, it does not explicitly specify when to use this tool versus alternatives (e.g., when to update versus add or delete a comment), leaving the usage context somewhat implied.

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