clear_issue_checklist

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

Discloses destructive nature with confirmation requirement. No annotations provided, but description covers basic behavioral trait. Lacks details like permissions or irreversibility.

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 sentences: first conveys purpose, second adds essential warning. No fluff.

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?

Sufficient for a simple delete tool with one parameter. Provides purpose and behavioral hint. Could mention return status or error cases but not critical.

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?

Only parameter 'issue_key' has no description; schema coverage is 0%. Description does not explain its meaning or format, leaving the agent to infer from name.

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?

Clearly states 'Deletes the entire checklist on an issue (all items at once)', specifying the exact verb and resource. Distinguishes from sibling 'delete_checklist_item' which deletes individual items.

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?

Explicitly warns that it is destructive and requires user confirmation. No mention of when not to use or alternatives, but context implies using for bulk deletion.

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