crm_delete

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

The description adds a significant behavioral trait—user confirmation is required—beyond what the annotations (destructiveHint, readOnlyHint, openWorldHint) already convey. It provides useful context about the interaction flow without contradicting any annotation.

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?

The description is extremely concise—two short sentences—with the purpose front-loaded and the confirmation requirement following. No filler or 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 operation with only two documented parameters and an output schema present, the description covers the essential behavioral requirement (confirmation) and the entities involved. It does not explain return values, but the output schema likely handles that.

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 description coverage is 100% for both parameters (id and entity) with clear descriptions and an enum. The tool description itself adds no additional parameter-level detail, so the baseline 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 action 'delete' and the specific CRM entities it applies to (lead, deal, contact, company), which matches the schema enum. This distinguishes it from siblings like crm_create, crm_update, and crm_list.

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 deleting CRM entities and adds that user confirmation is required, giving clear usage context. It does not explicitly mention alternatives, but the purpose is unambiguous given the tool name and sibling set.

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