Delete Issue Comment

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

The description confirms a deletion operation, aligning with annotations (readOnlyHint: false). However, it does not disclose irreversibility, permissions required, or what happens to associated data (e.g., notifications). The annotations partially cover the behavioral burden, but the description adds minimal extra context.

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 a single, front-loaded sentence that efficiently conveys the core action. No extraneous words.

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 simplicity of the tool (two parameters, no enums, output schema exists), the description provides the basic purpose but lacks details like idempotency behavior or error scenarios. This is adequate but not thorough for an agent to fully understand invocation context.

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% with both parameters described (issue_id format, comment_id type). The description does not add additional semantics beyond what the schema already provides, so baseline 3 is appropriate.

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 'Delete a comment from a Yandex Tracker issue' clearly states the verb (delete), resource (comment), and context (Yandex Tracker issue). It distinguishes from sibling tools like issue_add_comment or issue_update_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?

No guidance is provided on when to use this tool vs alternatives, such as issue_update_comment for editing. There are no prerequisites, permissions, or when-not-to-use hints, leaving the agent to infer usage context.

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