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

Annotations already indicate readOnlyHint, idempotentHint, and destructiveHint, making the tool's safe nature clear. The description adds the behavioral trait of bulk execution via the 'ids' parameter, which is positive but not comprehensive. No contradictions with annotations.

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?

Two sentences with no fluff. The first sentence directly states the core purpose, and the second adds a key usage note. Highly efficient and front-loaded.

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 simple, but without an output schema, the description omits any detail about the return structure. For a 'get' tool, this is acceptable but leaves the agent without clarity on the response format. Complete enough for basic invocation but not fully comprehensive.

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 description coverage is 0%, so the description must compensate. It adds meaning for 'id' (implicitly) and 'ids' (bulk support), but does not address the 'account' parameter. Partial improvement over the schema, but incomplete.

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 'Detalhe de uma venda por id' clearly states the function is to retrieve details of a specific sale by its ID. This distinguishes it from sibling tools like 'contaazul_list_sales' that list multiple sales, and other get tools that focus on different entities.

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 when you have a sale ID, but does not explicitly state when to use this tool versus alternatives like 'contaazul_list_sales'. The bulk support note provides some usage context but no clear when-not or alternative guidance.

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