Delete Checklist Signature Request

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

Annotations already declare destructiveHint true and readOnlyHint false. The description adds 'cannot be undone' and 'permanently removes', reinforcing the irreversible nature. However, the inaccuracy about inspections reduces trust in the description's reliability.

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 relatively short but contains redundant phrases ('This cannot be undone' repeated twice) and includes API endpoint info that may not be necessary for an AI agent. It could be more streamlined.

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 no output schema, the description does not explain return values or confirm deletion outcome. It does mention required parameters and the destructive effect, but the confusion over what is deleted (inspections vs signature request) leaves gaps in contextual understanding.

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?

Input schema has 100% description coverage for all parameters. The description merely lists the required parameters (project_id, list_id, id) without adding semantic details on how to obtain them or their relationships beyond what the schema provides.

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 it deletes a Signature Request for a specified Checklist, but then repeatedly says it deletes 'the specified Inspections', creating confusion about the actual resource. This inconsistency undermines clarity and could mislead an AI agent.

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 explicit guidance on when to use this tool versus alternatives (e.g., delete_checklist_signature or delete_checklist_inspection). The description only provides a generic statement about permanent deletion without context on prerequisites or exclusions.

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