olist_contato_obter

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 states the endpoint and provides a documentation link; it does not disclose what the tool returns, whether it can fail, required permissions, or any side effects. The verb 'Obter' implies a read operation, but no further behavioral traits are described.

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 contains no wasted words, but it is under-specified. It front-loads the tool name and endpoint, yet it does not provide enough useful content to be considered well-structured for an agent.

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 simple (one required parameter, no output schema), but with no annotations and no description of return values or error behavior, the description is incomplete. The documentation link is useful but does not substitute for inline guidance about what the tool does or when to use it.

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 describes the single parameter 'id' as 'Número de identificação do contato na Olist' with 100% coverage, so the description does not need to add much. It adds no parameter-level details beyond the schema, but the baseline of 3 is appropriate because the schema already covers the parameter fully.

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 identifies the operation as 'Obter Contato' and specifies the API endpoint 'contato.obter', giving a specific verb and resource. However, it does not explicitly differentiate this from the sibling search tool 'olist_contatos_pesquisa' or mention that it retrieves a single contact by ID.

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 guidance on when to use this tool versus alternatives. No mention that it should be used when a contact ID is known, or that search should be used to find contacts. The endpoint name implies get-by-ID, but no explicit usage context or exclusions are provided.

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