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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered. The description adds the meaningful nuance that deletion is a soft delete, but omits whether it can be undone, whether attached notes/tasks/emails are cascade-detached, and what the response reports.

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 short sentence, front-loaded with the action and resource, with the important "soft delete" qualifier attached rather than buried. 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?

Output schema and annotations cover the return shape and safety profile, and the parameter is documented. Still, for a destructive CRM operation the description should say what happens to linked records and whether the soft delete is reversible; those are the gaps an agent would actually need.

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 required parameter with 100% schema description coverage, so the schema fully documents it. The description adds nothing about ID format or how to obtain a valid ID (e.g., via list-opportunities-tool), which is the baseline expectation when schema coverage is high.

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?

States a specific verb and resource ("Delete an opportunity") and clarifies the CRM synonym "deal", so the agent knows exactly what object is affected. It does not distinguish itself from other delete-tools or from update-opportunity-tool, but the resource naming makes confusion unlikely.

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?

No guidance on when to delete versus update/close an opportunity, no prerequisites (permissions, ownership), and no recovery instructions despite the parenthetical "soft delete". The agent must infer everything about when this is the right call.

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