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

The term 'soft-delete' adds important behavioral context beyond the destructiveHint annotation, indicating the deletion is reversible or retains data. No other side effects are mentioned, but the annotation already signals destructiveness.

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?

One concise sentence that front-loads the action and resource. Every word adds critical information, with no filler.

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 one-parameter mutation tool with annotations and an output schema, the description adequately conveys the core operation. It does not explain return behavior, but the output schema covers that aspect.

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?

The schema provides 100% coverage with dealId described as 'The deal ID to delete.' The description does not add extra meaning beyond the schema, so a 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?

The description clearly states the specific action 'soft-delete' and the resource, a 'CRM deal from the sales pipeline.' This distinguishes it from siblings like update_deal, mark_deal_lost, and mark_deal_won.

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?

The description implies the tool is for removing a deal from the pipeline, but it does not explicitly compare with alternatives like mark_deal_lost or update_deal_stage. There is no when-to-use or exclusions guidance beyond the soft-delete semantics.

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