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

Annotations already indicate readOnly and idempotent. The description adds key behavioral context: the tool returns a result with 'results' and 'errors' arrays (partial failure), and operates as a batch operation. This exceeds annotation coverage, though no details on authentication or rate limits.

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 relatively short but includes irrelevant details about other actions (list, get) that belong to sibling tools. The core get_many description is concise but could be more focused. It mixes languages (Portuguese/English) which may reduce clarity.

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?

Given the tool's complexity (6 parameters, no output schema), the description provides the essential purpose and return format but lacks parameter details and context on when to pass each field. It achieves a basic completeness score, but falls short for a production tool.

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 explains the 'order_ids' parameter and its batch purpose, but the input schema lists 6 parameters (data, page, size, account, order_id, order_ids) with 0% schema description coverage. The description neglects the other five parameters, leaving their meaning unclear. This is insufficient for effective tool invocation.

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 tool action: 'get_many: busca vários por order_ids (lote, retorna { results, errors })' and distinguishes it from 'list' and 'get' by specifying the method (batch by IDs) and return format.

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 use when needing multiple orders by specific IDs, and mentions the return includes both results and errors. However, it does not explicitly state when to avoid this tool or provide alternatives beyond the brief mention of other actions.

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