ml_detalhe_anuncio

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

Annotations indicate readOnlyHint, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds value by specifying the return format (JSON with common fields, description, images, seller, and error handling), which is beyond the annotations. It does not mention rate limits or authentication, but for a read-only tool this is acceptable.

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 extremely concise: two sentences for the main purpose, plus structured 'Args' and 'Returns' sections. Every part adds value without redundancy.

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 tool (1 param, no nested objects) with an output schema available, the description covers the purpose, input parameter, and return format (including error handling). It is complete given the context.

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 description restates the 'url' parameter and its purpose, which is already documented in the input schema. With schema description coverage at 0% (implying schema lacks descriptions, though the schema actually has one), the description adds minimal new meaning. Baseline 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 it retrieves details of a Mercado Livre listing from a URL, using the verb 'Obtém' (gets) and specifying the resource and platform. It is implicitly differentiated from siblings like ml_buscar_anuncios (search) and olx_detalhe_anuncio (OLX platform).

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, such as when to search vs. get details, or any prerequisites (e.g., valid URL format). It only states the action.

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