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

The description says the tool deletes a contact and includes '[write, altera dados]', yet annotations declare destructiveHint=false. This is an annotation contradiction: deleting a contact is inherently destructive. The description also does not disclose permanence, reversibility, or side effects beyond the contradictory write marker.

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 and front-loads the operation, but the '[write, altera dados]' tag adds little value and the 'Unidades:' prefix is cryptic. It is concise but not optimally structured for agent consumption.

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 operation with three undocumented parameters and no output schema, this description is far from complete. It omits the required payload, authentication/account context, and any behavior details about the deletion. An agent cannot reliably invoke this tool without guessing.

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 three string parameters (body, query, account) with 0% description coverage, and the description adds no meaning about what these parameters should contain or which are needed to identify the contact. An agent cannot determine how to construct a valid call.

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 'Excluir um contato' (delete a contact) and the endpoint POST /contatos/delete, identifying both the verb and resource. It distinguishes this from other deletion tools by the explicit contact resource, though it does not explicitly position it against 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?

No guidance is provided on when to use this tool versus alternatives, nor any prerequisites, conditions, or exclusions. The 'Unidades' prefix is unexplained and does not help an agent decide when this tool is appropriate.

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