olist_separacao_obter

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only implies a read operation via 'Obter' (get). It does not disclose return format, error behavior, authentication needs, or any side effects. This is a minimal disclosure not adding meaningful context beyond the tool's name.

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 short and to the point but structured as fragments: 'Obter Separação API 2.0. Endpoint API V2: separacao.obter. Documentação: ...'. It is not a clean single sentence, and the endpoint/doc info could be presented more cohesively. Still, it is concise and not wasteful.

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?

The tool is a simple one-parameter getter with no output schema and no annotations, so the description should at least clarify what the tool returns and how it differs from search. 'Obter Separação' is vague; it doesn't state that it returns a single separation by ID or mention any response details. The description is minimally sufficient but leaves gaps.

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 schema fully documents the single parameter 'idSeparacao' (100% coverage), so the parameter semantics are already covered. The description adds no extra meaning about the parameter, but the schema does. Baseline of 3 applies since the description does not need to compensate.

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 'Obter Separação' (Get Separation), a clear verb+resource combination. The endpoint 'separacao.obter' reinforces the action. However, it does not explicitly differentiate from sibling 'olist_separacao_pesquisa' or mention that it fetches by ID, though the name implies a single-record retrieval.

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?

The description provides no guidance on when to use this tool versus alternatives like 'olist_separacao_pesquisa'. The included documentation URL is a resource but not inline usage direction. No exclusions or alternative tool references are given.

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