delete_opportunity

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

Annotations already indicate destructiveHint=true. The description adds crucial details: irreversibility, need for confirm=true, idempotent behavior on retry, and the exact response format including 'alreadyDeleted' field. No contradiction with annotations.

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, no wasted words. Front-loaded with critical warning and requirement. Second sentence efficiently covers idempotency and response.

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?

Despite no output schema, the description fully covers response format, required parameter behavior, and safe usage pattern. Complements annotations well.

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 coverage is 50% (only confirm has description). The description adds meaning by stating 'confirm=true' requirement and explaining idempotent responses, but does not elaborate on the 'id' parameter beyond what 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 starts with 'DESTRUCTIVE & IRREVERSIBLE: permanently delete an opportunity.' The verb 'delete' and resource 'opportunity' are clearly stated, distinguishing it from sibling tools like delete_party or delete_project.

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 'Always read the opportunity first with get_opportunity and confirm with the user before calling.' Also specifies that confirm must be true, providing clear when-to-use and when-not-to-use guidance.

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