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

The description explicitly says 'Deletar', 'DELETE', and '[write, altera dados]', which are destructive/write semantics, while annotations set destructiveHint to false. This is a direct annotation contradiction and makes the tool's safety profile ambiguous.

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: two sentences that front-load the resource and operation, then add the bulk execution detail. No unnecessary filler.

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 multiple undocumented parameters, the description does not cover body/account semantics, response/error behavior, idempotency, or side effects. The destructiveHint mismatch further prevents the agent from invoking this tool confidently.

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%, and the description only adds meaning for the ids parameter via bulk support. The id is implied from the endpoint, but body and account are left entirely unexplained, so parameter semantics remain incomplete.

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 identifies the resource ('Campos extras de orçamentos') and the operation ('Deletar', 'DELETE /api/atributos_orcamentos/{id}'), and the name distinguishes it from create/get/list/update siblings.

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 explicit usage guidance is batch support ('accepts ids for batched execution'). There is no guidance on when to use this instead of related tools, whether id and ids are mutually exclusive, or how account/body parameters should be set.

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