deals_delete

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

Disclosure includes permanent and irreversible deletion, and notes that related activities and notes are preserved but detached. Despite no annotations, the description fully covers behavioral traits.

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?

Well-structured with clear sections: main action, warning, workflow tips, and common use cases. Every sentence earns its place, no redundancy.

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?

For a simple delete-by-id tool, the description covers all aspects: what it does, its permanence, alternative approaches, and example use cases. No output schema needed.

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 already describes the id parameter (100% coverage), but the description adds context with usage tips and concrete examples (e.g., 'Delete test deal: { "id": 123 }'), enhancing understanding.

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 clearly states 'Delete a deal permanently' and warns against accidental deletion, distinguishing it from alternatives like marking as lost. It differentiates from siblings such as deals_update and deals_mark_as_lost.

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 advises considering marking as lost instead, and provides workflow tips like verifying the deal with deals/get first. It tells when to use vs alternatives.

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