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

Annotation contradiction: the description says 'Excluir negócio' and uses HTTP DELETE, implying destructive behavior, while annotations declare destructiveHint:false. No soft-delete or reversible-delete qualification is provided to reconcile this mismatch. The '[write, altera dados]' note matches readOnlyHint:false but does not resolve the destructive conflict.

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 tightly written and front-loaded: it names the operation, gives the HTTP endpoint, flags it as a write operation, and notes bulk support. There is no filler or redundant prose.

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 four parameters, no output schema, and no schema-level descriptions, this definition is incomplete. It does not explain 'body' or 'account', mention return/error behavior, or clarify whether deletion is soft or destructive. The destructiveHint contradiction further undermines completeness.

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 endpoint clarifies the 'id' parameter and the bulk note gives meaning to 'ids', but 'body' and 'account' remain unexplained. With schema description coverage at 0%, the description needed to compensate for all parameters but does not.

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 operation ('Excluir negócio') and the exact endpoint (DELETE /api/v1/businesses/{id}), making it unambiguous that this tool deletes a business. It distinguishes itself from sibling get/list/patch/create tools and adds bulk support context.

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 provides a clear action and a bulk-use note ('accepts ids for batched execution'), implying when to use it. However, it does not explicitly state alternatives, prerequisites, or when not to use it, leaving usage guidance somewhat implicit.

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