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

Annotation Contradiction: the description says 'Deletar' (delete) and '[write, altera dados]' (changes data), implying a destructive mutation, while annotations declare destructiveHint=false. The description also does not disclose irreversibility, side effects, or response behavior beyond the raw DELETE HTTP verb.

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 two short, front-loaded sentences. The first states the operation and resource; the second adds the only non-obvious usage detail (bulk support). No filler or unnecessary repetition.

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 delete tool with no output schema and minimal annotations, the description should explain parameter roles, expected outcomes, and safety aspects. It only covers the basic delete and bulk support, omitting `body`, `account`, and any error/response context; the annotation contradiction further reduces trust.

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 schema has 4 parameters with 0% description coverage. The description only clarifies that `ids` enables batch deletion and implies `id` is the single identifier. It leaves `body` and `account` completely unexplained, so the agent cannot determine their purpose.

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: 'Deletar' (delete) for 'Campos extras financeiros' and provides the explicit DELETE endpoint. The resource scope distinguishes it from sibling delete tools for cadastros, orcamentos, ordens_servicos, etc.

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 gives useful bulk execution guidance ('accepts ids for batched execution') and the delete verb implies when to use it. However, it does not explicitly contrast with create/update/list/get siblings or explain when to use single `id` versus `ids`.

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