leboncoin_listing

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

With no annotations, the description carries the behavioral burden and does well by listing exclusions (seller identity and contacts, precise location, payment, delivery, account data). This prevents the agent from expecting data the tool cannot return, though it doesn't address error handling or non-listing URL behavior.

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 two sentences with no filler. The core action is front-loaded, and the exclusions are packed into a compact second sentence.

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 single-parameter detail lookup with no output schema, the description covers what the agent needs: what it returns and what it intentionally omits. Missing details about the exact shape of the normalized metadata are understandable given the low complexity, and the exclusions provide important guardrails.

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 parameter description already states the URL must be a canonical public ad from leboncoin-search. The tool description adds little beyond 'one supplied Leboncoin ad URL', so it does not meaningfully augment 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 states a clear verb-resource pairing: get a Leboncoin public listing for one supplied ad URL. It also explicitly differentiates from the sibling tool leboncoin_search by describing the detail-level operation rather than searching.

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 usage by saying it takes one supplied URL, and the schema parameter notes the URL must come from leboncoin-search. However, it does not explicitly state when to use this tool versus the search sibling, or what scenarios should avoid it.

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