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

The description says 'Remove' (destructive) while annotations set destructiveHint=false, directly contradicting. No additional behavioral context is given, such as irreversibility, permissions, or impact on related data, making the tool's actual behavior ambiguous for agents.

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 a single, front-loaded sentence with no fluff. It conveys the core action efficiently, though it is terse and omits necessary details.

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 deletion tool with no output schema and contradictory annotations, the description fails to provide essential context: it does not explain idempotency, failure outcomes, or account scope. The minimal description leaves agents guessing about side effects and dependencies.

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?

With 0% schema description coverage, the description must compensate. It clarifies 'ids' (one or more records) and 'object' (de um objeto), but leaves 'account' unexplained. The mapping is partial and does not fully clarify all parameters.

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 specifies the action ('Remove um ou mais registros') and the resource ('de um objeto por id'), distinguishing it from sibling delete tools like crm_delete_file and crm_delete_object. It directly addresses the tool's purpose.

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 is provided on when to use this tool versus alternative deletion tools or other record operations. The description only states the action without contextualizing usage scenarios or exclusions.

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