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

The annotations declare destructiveHint: false, but the description explicitly says 'Deletar' (DELETE), which is inherently destructive. This is a direct annotation contradiction. Additionally, the description only provides the redundant '[write, altera dados]' note and does not disclose irreversibility, missing-resource behavior, or other consequences.

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 compact sentences: the first states the purpose and endpoint, the second mentions bulk support. It is front-loaded and contains no fluff.

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 deletion tool with four parameters and misleading annotations, the description omits critical details about 'body' and 'account', irreversibility, and error behavior. It does not provide enough information for an agent to invoke the tool with confidence.

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 description explains the 'id' parameter via the endpoint path and the 'ids' parameter via the bulk support note, but leaves 'body' and 'account' unexplained. With zero parameter descriptions in the schema, this partial compensation does not fully clarify all four parameters.

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 'Deletar' (Delete) and the endpoint DELETE /api/recebimentos/{id}, unambiguously identifying this as a delete operation for recebimentos. This distinguishes it from siblings such as create, get, list, and update.

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 recebimentos and adds bulk support via 'ids', but it does not explicitly state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. The usage context is clear but not formally articulated.

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