Delete Request

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

Reinforces annotations' destructiveHint: true and adds scope limitation: 'does not delete anything on remote FYI/Alaveteli sites.' Provides context beyond annotations, though could mention error handling 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?

Three concise sentences, no redundancy. Important information front-loaded. Every sentence contributes value.

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, scope, usage guidelines, and alternatives. Simple one-parameter delete tool—description is thorough enough for correct tool selection and invocation.

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?

Single parameter with 100% schema coverage. Description does not add extra meaning beyond schema's 'Stable local request ID to delete permanently.' Baseline score of 3 is appropriate.

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 'Permanently delete a local request and all of its stored correspondence from SQLite' with specific verb and resource. Distinguishes from sibling tools by naming update_request for edits and list_requests/retrieve_request for inspection.

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 instructs to use only after confirming ID should be discarded, and provides clear alternatives (update_request for edits, list/retrieve for inspection). Notes destructive and irreversible nature.

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