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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds bulk batching behavior and parameter-to-action mapping, but leaves 'Flattened action: offers' unexplained and doesn't mention pagination, authentication, or return behavior beyond the available filters.

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 compact and front-loaded with the core purpose, then uses a clear action/parameter list and a separate bulk-support note. The '[Flattened action: offers]' line is cryptic and consumes a sentence without adding clear value, preventing a perfect score.

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?

For a 12-parameter tool with no output schema, the description covers actions, filters, section enum, and bulk execution, which is substantial. Yet it lacks an explanation of how the tool selects an action given that the schema has no 'action' field, and it omits the 'account' parameter and any return-value guidance.

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?

With 0% schema description coverage, the description compensates well by mapping parameters to each action (e.g., list uses name, type, marketplace_id, is_hidden, cursor; checkout_options uses product_id + section) and by explicitly enumerating valid section values. However, the 'account' parameter is not mentioned anywhere, and the semantics of 'is_hidden' and 'type' values are left to inference.

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 this is a read-only tool for 'Produtos e ofertas no Guru' and enumerates specific actions (list, get, offers, offer, etc.). It is more specific than the bare tool name, though 'Flattened action: offers' adds some confusion and sibling differentiation is not explicit.

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 gives useful context by saying 'leitura' and listing which parameters belong to which action, plus bulk support for arrays. However, it does not explicitly say when to choose this tool over similar sibling tools like guru_products_get, guru_products_list, or guru_products_offer.

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