delete_checklist_item

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered structurally. The description adds value beyond that by stating the change is irreversible and affects the parent issue, and by requiring user confirmation — a workflow constraint the annotations do not express. It still omits any permission or rate-limit 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?

Two short sentences with zero filler: the action is front-loaded and the irreversibility/confirmation warning follows. Every clause earns its place.

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?

An output schema exists so return values need no explanation, and the annotations cover destructiveness. What is missing is the parent/child relationship between issue_id and checklist_item_id, which an agent needs to call the tool correctly. The description is adequate but leaves that identifiable gap.

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 description coverage is 0% for two required parameters, so the description carries the full burden. It refers obliquely to the checklist item identifier ('подтвердите идентификатор пункта') but never explains issue_id or the relationship between the two IDs, leaving half the parameters unexplained.

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 states a specific verb+resource ('Удалить один пункт чек-листа' — delete one checklist item), which is clearly distinguishable from the add_/update_checklist_item siblings. It stops short of naming an alternative or clarifying where the item lives, so it is clear but not maximally differentiated.

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?

It gives one actionable precondition — confirm the item ID with the user before deleting — which is genuine usage guidance for a destructive operation. However, it names no alternatives (e.g. update_checklist_item) and states no when-not-to-use condition, so the routing guidance is only implied.

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