olist_contatos_pesquisa

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only says 'Pesquisar' and gives the endpoint, but does not disclose pagination behavior, whether results are read-only, the return structure, authentication requirements, or any filtering semantics beyond what the schema provides.

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 concise sentence containing the API version, endpoint, and documentation URL. It is front-loaded with the key purpose, though the API version and endpoint are slightly redundant.

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?

With 8 parameters, no output schema, and no annotations, the description lacks essential context such as pagination, intended use cases, and return value expectations. The documentation link helps but does not make the description self-sufficient for an agent to invoke the tool correctly.

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 descriptions for all 8 parameters (100% coverage), so the baseline is 3. The description adds no parameter-level meaning beyond the endpoint and documentation link, but the schema itself is adequate for understanding each field.

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 'Pesquisar Cadastros API 2.0' and specifies the endpoint 'contatos.pesquisa', clearly identifying a contact search operation. It distinguishes from sibling tools like olist_contato_obter and olist_contato_alterar by using the 'pesquisar' verb, though 'Cadastros' is a bit generic and does not explicitly say 'contacts' except in the endpoint.

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?

No usage guidance is provided. The description only gives the endpoint and documentation link, with no mention of when to use this search versus alternatives like olist_contato_obter for retrieving a specific contact or olist_contato_incluir for creating one.

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