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

The description includes '[write, altera dados]' indicating the tool modifies data, which is helpful since the destructiveHint is false. It also discloses bulk support (accepts ids), adding behavioral context beyond the annotations. However, lacks details on irreversibility or consequences of deletion, but with annotations lacking destructiveHint, this is still valuable.

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 concise: two lines covering purpose, endpoint, and bulk support. It is appropriately short, though could add a brief note on the 'account' parameter. No waste words overall.

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 4 parameters, the description covers the core action and bulk capability, but leaves gaps: no mention of how 'id' vs 'ids' relate (mutually exclusive?), no detail on 'body' or 'account', and no explanation of response. Given the tool's simplicity, it's adequate but not complete.

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 input schema has 4 parameters with 0% description coverage, so the description needs to compensate. It mentions 'ids' for bulk and implies 'id' from the endpoint, but does not explain the purpose of 'body' or 'account'. Provide insufficient detail for the parameters, especially given no schema descriptions.

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 it deletes extra product fields via DELETE /api/atributos_produtos/{id}, and includes '[write, altera dados]' indicating modification. It distinguishes from sibling tools by specifying the resource (produtos) and operation (delete), though the title already conveys this.

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?

It mentions bulk support with IDs, implying usage when multiple entries need deletion, but does not explicitly contrast with alternatives (e.g., 'use update to change fields') or specify when not to use. The endpoint and write intent give some context, but there's no clear when-to-use guidance beyond the operation itself.

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