delete_checklist_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool 'Removes' an item, implying a destructive operation, but fails to mention any side effects, permissions required, error handling (e.g., if item not found), or whether the operation is idempotent. This minimal disclosure is insufficient for safe invocation.

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 consists of two short sentences, no superfluous words, and immediately delivers the core purpose and a critical prerequisite. Every word 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?

For a deletion tool with no output schema and no annotations, the description should cover return behavior, side effects, and error scenarios. It only states the action and a prerequisite, omitting whether deletion is reversible, what happens on success/failure, or any post-condition. This leaves too many gaps for an agent to operate safely.

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?

With 0% schema description coverage, the description must compensate. It adds limited meaning by noting that item_id comes from list_checklist_items, but does not explain issue_key's purpose or format, nor provide any constraints or examples for either parameter. The schema itself gives only type and required status, so the description adds marginal 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?

The description clearly states the action ('Removes a single checklist item') and the resource ('from an issue'). It distinguishes this tool from siblings like add_checklist_item (adds), clear_issue_checklist (removes all), and update_checklist_item (modifies). The verb is specific and the scope (single item) is explicitly noted.

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 a prerequisite: 'Requires the checklist item id from list_checklist_items,' which guides the agent to first fetch IDs. However, it does not explicitly state when to use this tool versus siblings (e.g., for multiple deletions use clear_issue_checklist) or mention alternative approaches. The context is clear but lacks exclusionary guidance.

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