b24_crm_delete

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

Annotations already set destructiveHint=true, so the description's 'Irreversible' adds contextual emphasis beyond that. It confirms the operation's permanence, which aligns with the tag. No contradiction; the description enriches the behavioral understanding without repeating 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 crisp sentences with no wasted words. The purpose is front-loaded in the first sentence, and the irreversible warning is placed immediately after. Every sentence adds value without 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?

Given the simplicity of a delete operation and the presence of a detailed input schema, output schema, and annotations, the description covers the essential behavioral context (irreversibility). It could mention permission requirements or return value hints, but overall it is sufficiently complete for an agent to infer correct usage.

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 100% with detailed parameter descriptions (e.g., entity_type_id for SPA). The tool description offers no additional parameter-level explanation beyond what the schema provides. Baseline 3 is appropriate as the schema already handles semantics.

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?

Clearly states the action ('Delete') and target ('CRM record'), with the additional emphasis 'Irreversible — deletes on the portal.' This verb+resource definition is specific and distinguishes it from other CRM tools like update or list. No ambiguity.

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 usage when deletion of a CRM record is needed, but it lacks explicit guidance on when not to use or alternatives. For instance, it does not compare with sibling delete tools (e.g., b24_calendar_event_delete) or note prerequisites like entity type. Usage is clear but not comprehensively guided.

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