Delete report drafts

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

Annotations already indicate destructive and non-idempotent behavior. The description adds that deletion is permanent and limited to Draft or Returned status. No contradictions. Could further clarify prerequisites or side effects.

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, front-loaded with action and resource, followed by usage condition. No redundant information.

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?

Covers purpose, security requirement, and scope. Missing mention of prerequisite steps (e.g., obtaining the deletion token from another tool) and potential error handling, but sufficient for a simple destructive operation.

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 50% (only 'confirm' has a description). The tool description adds context by mentioning 'deletion token' but does not elaborate on the token format or how to obtain it. Moderate compensation.

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 explicitly states the verb 'delete' and the resource 'Draft or Returned CamCORS reports' using a 'deletion token'. It clearly distinguishes from sibling tools that handle other actions like submission, preparation, or editing.

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?

Provides a strong condition: 'Call only after the user has reviewed the exact reports and explicitly confirmed deletion.' This guides the agent on when to invoke. Could be improved by mentioning alternative workflows, such as using camcors_prepare_report_deletion first.

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