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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description earns credit for disclosing the three terminal/intermediate states and that failures return the error, which is real behavioral context not available from annotations or schema (no output schema exists).

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?

A single compact sentence with the core information front-loaded. Efficient, though slightly telegraphic and the '(cancelamento)' aside is less prominent than it deserves.

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?

With no output schema, describing the possible states is genuinely necessary and done well. However, for a polling tool the description omits how the operacao_id is obtained and any polling guidance, leaving meaningful gaps for correct invocation.

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 single parameter operacao_id has 0% schema description coverage, and the description says nothing about it — no format, no indication that the id comes from cancelar_nota. The description fails to compensate for the schema gap.

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?

States a specific resource (operação) and its status check, and enumerates the possible outcomes (processando, concluida, falhou com erro). It does not differentiate from the near-identical sibling acompanhar_pedido, leaving the agent to infer the target object from the name alone.

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 parenthetical '(cancelamento)' hints this is used to poll a cancellation operation, but there is no explicit statement of when to call it, how often to poll, or why one would choose it over acompanhar_pedido. Usage is implied rather than specified.

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