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

Annotation Contradiction: The description states 'Deletar' and 'altera dados', indicating a destructive write operation, but the annotations set destructiveHint=false. This is a serious inconsistency. The description also does not disclose irreversibility, authorization requirements, or effects of bulk deletion beyond the annotation contradiction.

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 compact, front-loaded with the resource and operation, and includes the HTTP method. It avoids fluff, though the bulk-support note could have been integrated more naturally.

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?

With no output schema, sparse annotations, and four parameters at 0% schema description coverage, the description is under-specified. It does not explain required vs optional parameters, response behavior, error cases, or the distinction between deleting and canceling a service invoice.

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 0%, so the description carries the burden for explaining parameters. It only clarifies that 'ids' enables batch deletion, and implies 'id' is the single-item identifier. It leaves 'body' and 'account' unexplained, which is insufficient for correct invocation.

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 ('Deletar'), the resource ('Notas Fiscais de Serviços'), and the exact HTTP endpoint (DELETE /api/notas_fiscais_servicos/{id}). It also indicates write semantics and bulk capability, making it easy to distinguish from sibling get/list/create/update/cancelar tools.

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 for deleting service invoices and explicitly notes bulk support via 'ids'. However, it does not mention when to prefer delete over the sibling 'cancelar_create' tool, nor does it provide exclusions or alternative guidance.

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