olist_contrato_adicional_pesquisa

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

No annotations are provided, so the description carries the full burden. It only says 'Pesquisar' (search) and provides an endpoint and documentation link, but it does not confirm read-only behavior, disclose return format, pagination, permissions, or potential side effects. The basic search intent is clear, but no substantial behavioral context is added.

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 concise and front-loaded: it states the purpose, the API endpoint, and a documentation link in two short sentences. Every part earns its place with no redundancy or filler.

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?

Despite the tool being simple (one parameter, no output schema), the description omits crucial context such as what the search returns, any pagination behavior, and when to use it relative to similar tools. The documentation link may provide details, but the description itself is insufficient for an agent to fully understand the tool's behavior and output.

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 input schema already provides 100% coverage for the single parameter idContrato with a clear description ('Id do contrato que será pesquisado'). The tool description does not add any additional parameter semantics beyond what the schema already states, so the baseline score of 3 is appropriate.

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: 'Pesquisar Adicionais de Contrato' (Search Contract Add-ons), which clearly distinguishes it from sibling tools like olist_contrato_adicional_incluir/excluir and olist_contratos_pesquisa. The API endpoint reference reinforces the exact operation.

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?

There is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites. The name and verb imply a search operation, but the description does not state when this should be chosen over related tools like olist_contrato_obter or olist_contratos_pesquisa.

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