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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds that the tool supports bulk execution via 'ids', providing extra behavioral context beyond the annotations. No contradictions; it enhances transparency regarding batch capabilities.

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 extremely short—two sentences—and gets straight to the point. It front-loads the purpose and adds a key detail about bulk support. No filler or redundancy.

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 has 4 parameters and no output schema, so the description should explain return values and remaining parameters. It explains the core read purpose and batch, but omits details about what the response contains, the meaning of 'query' and 'account', and how it differs from the list tool. Given the complexity (average), this is a moderate gap.

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 explain parameters. It clarifies 'id' (referenced in the endpoint) and 'ids' (for batch), but 'query' and 'account' remain unexplained. It compensates partially but not fully, leaving two parameters ambiguous.

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 says 'Campos extras vendas: Visualizar' (View extra sales fields) and specifies the GET endpoint, making it clear this is a read operation for a specific resource. It distinguishes from create/delete/update siblings by the verb 'Visualizar' and the GET method, though it doesn't explicitly compare to the list sibling.

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 'accepts ids for batched execution', which hints at using this tool when you have multiple IDs. However, it doesn't explicitly state when to use this instead of the list tool or single GET, nor does it mention any alternatives. Usage context is implied but not fully articulated.

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