Delete Issue Checklist Item

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

Annotations already declare destructiveHint=true, and the description adds useful behavioral detail beyond that: it confirms the operation deletes a single item and states the return behavior, "Returns the issue's checklist after the deletion." This helps the agent set expectations about the side effect and response.

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?

Three short sentences carry all the essential information: the action, the prerequisite lookup step, and the return behavior. No filler or redundant repetition of the schema.

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?

The tool is low-complexity with two fully documented required parameters, a destructive annotation, and an output schema. The description adds the only practical missing piece—how to find the checklist item ID—and states the return value. Nothing else an agent needs is absent.

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 already covers both parameters thoroughly at 100% coverage. The description adds value by telling the agent exactly how to obtain checklist_item_id via issue_get_checklist, which supplements the schema's static field description with a practical source for the value.

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?

Description uses a precise verb-resource combination: "Delete a single item from the checklist of a Yandex Tracker issue." It clearly distinguishes this from sibling tools like issue_delete_link or issue_delete_comment by naming the specific checklist-item resource.

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?

Description provides clear context and a concrete prerequisite: "Use issue_get_checklist to get the item IDs." It does not explicitly mention when not to use this tool or contrast it with checklist update/add alternatives, but the usage context is unambiguous.

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