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

The description says 'DELETE' and 'Deletar', but the annotations set `destructiveHint` to false, which contradicts the destructive nature of the operation. The description does not add helpful behavioral context such as permanent deletion effects, authorization requirements, or side effects.

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 short, front-loaded, and includes the HTTP method and a bulk-support note in a compact format. There is minor redundancy between 'Deletar' and 'DELETE', but the extra line about bulk execution is useful.

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 mutation/delete tool with no output schema and minimal annotations, the description leaves important gaps: it does not explain what `body` or `account` mean, what happens when the deletion succeeds, or whether bulk execution has restrictions. The contradictory destructive hint further weakens the operational context.

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 needed to explain the parameters. It explains that `ids` can be used for batched execution, but it does not clarify the meaning or format of `id`, `body`, or `account`.

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 tool deletes consumer invoices (Notas Fiscais de Consumidores) using the DELETE endpoint and provides the path with `{id}`. The verb and targeted resource are explicit, and the domain in the name disambiguates it from other delete tools like those for products or services.

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 only operational hint is that the tool supports `ids` for batched execution. There is no mention of when to choose this tool over related operations such as cancel, create, update, or the other delete tools, and no exclusions are provided.

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