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

The description states 'Deletar' (delete) and '[write, altera dados]', indicating a mutating operation. However, the annotation destructiveHint is false, which directly contradicts the nature of a delete operation. This contradiction warrants a score of 1.

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 extremely concise, with the primary purpose stated first and bulk support noted second. No extraneous words, perfectly front-loaded and efficient.

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 tool with 4 parameters, no output schema, and conflicting annotations, the description is too sparse. It omits details on return values, error handling, authentication, and does not clarify the use of multiple parameters. The contradiction further reduces completeness.

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 only mentions 'ids' for bulk support, but does not clarify the purpose of the 'body', 'account', or the relationship between 'id' (required) and 'ids'. With 0% schema description coverage, the description fails to compensate for missing parameter details.

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: 'Fornecedores: Deletar (DELETE /api/fornecedores/{id})' identifies the resource (fornecedores) and the action (delete). It also mentions bulk support, making it distinct from other delete tools for different resources.

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 suppliers, and the bulk support note provides a clear scenario for using the tool with multiple IDs. It does not explicitly contrast with alternatives, but the purpose is clear enough that an agent knows when to invoke it.

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