olist_notas_fiscais_pesquisa

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'search invoices' and provides an endpoint. It does not mention read-only nature, pagination behavior, response format, or any caveats. The documentation link is an external resource, not in the description itself.

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 very concise, consisting of one sentence plus a link. It front-loads the purpose, then gives endpoint and docs. The repetition of 'API 2.0' and 'API V2' is slightly redundant, but overall it's efficient.

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 having 12 parameters and no output schema, the description is minimal. It doesn't explain how filters interact, the meaning of pagination (e.g., 'pagina'), or what the response looks like. The documentation link helps, but the description itself is incomplete for a tool with this complexity.

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 100%, so the input schema already documents all 12 parameters with descriptions. The description adds no additional meaning beyond stating the endpoint, so the baseline 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 clearly states the tool searches for invoices ('Pesquisar Notas Fiscais'), with a specific verb and resource. It also mentions API 2.0 and the endpoint, but does not explicitly differentiate from sibling tools like 'olist_notas_servico_pesquisa' (service invoices) or 'olist_nota_fiscal_obter' (get single invoice), so it misses the full distinction.

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 alternatives. The description simply states what it does and includes a documentation link, but lacks any context about suitable scenarios, exclusions, or prerequisites.

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