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

The annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the description does not need to repeat safety. It adds useful context about filtering and ordering, but does not mention rate limits, authentication, or return behavior.

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 a single front-loaded sentence with no filler. Every clause contributes to purpose, filters, or ordering.

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 parameter schema, annotations, and lack of an output schema, the description covers the key behavior an agent needs to call the tool. It is only missing explicit sibling routing guidance and return-value context, which are secondary here.

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 coverage is 80%, so the schema already documents most parameters well. The description reinforces preco_maximo, desconto_minimo, and the sort options, but does not add meaning beyond the schema for termo or limite.

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 states a specific verb and resource ('Busca ofertas'), names the platform (Shopee Brasil), and specifies filters and ordering. It is clear, but it does not explicitly contrast with siblings like ofertas_da_categoria, ofertas_em_alta, or search.

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?

Usage is implied by the mention of maximum price, minimum discount, and ordering options, suggesting it is for filtered product searches. However, it gives no explicit when-to-use guidance, exclusions, or alternatives among the sibling tools.

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