olist_vendedores_pesquisa

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

With no annotations provided, the description carries full responsibility for behavioral disclosure, but it only repeats the action 'search sellers.' It omits critical behavioral details such as pagination behavior, response format, search semantics, and any prerequisites or side effects, making it entirely uninformative about how the tool behaves.

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 concise but not well-earned: the first sentence restates the tool name, and the second provides an endpoint identifier and documentation link. It could be improved by adding substantive behavioral or usage information in the same amount of space.

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 simple search tool with no output schema and no annotations, the description should at least mention return values, pagination, or search scope. It provides none of this, instead deferring to an external documentation link, leaving the agent with insufficient context to invoke the tool confidently.

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 both parameters (pesquisa and pagina), achieving 100% schema coverage. The description adds no extra parameter meaning beyond pointing to an external documentation URL, 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 'Pesquisar Vendedores' is essentially the same as the tool name (olist_vendedores_pesquisa), restating the resource without adding functional detail. The additional endpoint and documentation link do not clarify the tool's purpose beyond what the name already implies.

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 guidance is provided on when to use this tool versus the numerous sibling search tools (e.g., olist_contatos_pesquisa, olist_produtos_pesquisa). There is no mention of context, exclusions, or alternatives, leaving the agent to guess based solely on the name.

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