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

The description claims 'write, altera dados' but the annotations indicate destructiveHint: false, which contradicts the very nature of a delete operation. This is a direct contradiction. Additionally, the description does not disclose any side effects, dependency impacts, or reversibility, leaving the agent without adequate behavioral expectations.

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, using two sentences, and front-loads the main purpose. However, it omits valuable information that could be added without bloating, so it is slightly under-specified for its importance.

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?

The tool is a delete with bulk support, no output schema, and 4 parameters. The description fails to explain how bulk executes (e.g., partial failures), the meaning of 'account', whether deletion is permanent, or any prerequisites. It is incomplete for safe and correct use.

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 coverage is 0%, so the description carries the burden. It mentions 'id' and 'ids' (bulk) but fails to explain 'body' or 'account'. It does not clarify required vs. optional, format, or interaction between id and ids. Only vague hints are given, far from sufficient for the 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 the action: 'Ordens de serviços: Deletar' and provides the endpoint (DELETE /api/ordens_servicos/{id}). It unambiguously indicates this tool deletes service orders, distinguishing it from sibling tools like get, list, update, and create.

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 does not explicitly state when to use this tool versus alternatives. It mentions bulk support but no exclusions or recommended scenarios. Usage is implied from the tool name and context, but no guidance is given about when to use delete vs. other operations.

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