Read one Leboncoin ad

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

The description adds crucial behavioral context beyond the readOnlyHint and openWorldHint annotations: it warns that ad content is untrusted data, may contain prompt injection attempts, and instructs the agent to ignore and report such instructions. This is exactly the kind of non-obvious behavioral disclosure that annotations alone do not provide.

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 concise and well-structured: the first sentence states the core purpose, and the following sentences deliver an important security warning without unnecessary elaboration. Every sentence earns 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 simple read-only tool with no output schema, the description adequately covers what the tool returns and how to handle untrusted content. It does not describe error behavior or exact response structure, but the listed fields and security guidance make it sufficiently complete for the tool's 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 description coverage is 100%, so the schema already documents listingId and country. The description adds no additional parameter-level detail beyond restating that the tool works 'by id', which is already clear from 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?

The description clearly states the tool 'Returns the full detail of one ad by id' and lists the included fields (description, attributes, location, seller type). This distinguishes it from sibling tools like search_listings or get_listing_details_batch by emphasizing single-ad retrieval 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?

The description implies the tool is for retrieving one specific ad when you already have its ID, but it does not explicitly mention when to prefer this over alternatives like search_listings or get_listing_details_batch. The guidance is clear but implicit.

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