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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior. The description adds domain-specific transparency by saying it is consultation-only and does not sell, reserve, or deliver products, plus a geographic coverage limit. The phrase about following the ChatGPT connector contract adds little actionable information.

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 important details are front-loaded: full offer text by id from search, examples, coverage limit, and read-only behavior. It is efficient overall, though 'segue o contrato do conector do ChatGPT' is vague and does not clearly earn its place.

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 one-parameter lookup tool with full schema coverage, full annotations, and an output schema, the description covers purpose, id source, geographic scope, and non-transactional behavior. The main remaining gap is sibling differentiation from get_offer, which keeps it short of a 5.

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%, and the single parameter is already documented as the offer_id returned by search. The description reinforces that the id comes from search but adds no format, validation, or edge-case guidance beyond the schema.

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?

States a specific action and resource: return the full text of an offer by id obtained from search. This is clearer than the generic name 'fetch', but it does not explicitly distinguish itself from the sibling get_offer, which appears to cover similar detail 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?

Gives clear usage context: use the id returned by search, and examples such as 'detalhe da oferta' and 'endereço do mercado dessa oferta'. It also states a clear exclusion (only Joinville/SC, not other cities), though it does not explicitly say when to use get_offer or search_offers instead.

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