Detail d'une annonce Leboncoin

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

Annotations already declare readOnlyHint and openWorldHint, so the description only needs to add useful context; it lists the ad attributes and the presence of seller_id, which is helpful. It does not cover error cases, authentication needs, or rate limits, but for a simple read-only operation this is not a major omission. No contradiction with annotations.

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 one efficient sentence: the purpose is front-loaded, followed by a colon-separated list of returned content. There is no filler or redundancy; every part adds useful information.

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 read-only tool with an output schema and openWorldHint, the description is largely sufficient and even enumerates the expected output fields. It could be slightly stronger with explicit sibling routing or failure behavior, but nothing essential for a correct call is missing.

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 input schema already documents the only parameter fully: 'Identifiant numerique ou URL de l'annonce.' The description adds no additional parameter-level semantics or format guidance, so the baseline score of 3 applies.

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 specific verb and resource: 'Detail complet d'une annonce' and lists the exact contents returned (description, photos, attributes, contact info, favorites, seller_id). This makes the tool's purpose unambiguous and distinguishes it from siblings: it returns full detail of one ad, not search results or seller data.

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 right context: use this tool when full details of a single ad are needed, identified by an ad ID or URL. However, it does not explicitly say when not to use it or mention alternatives such as search_ads for listing discovery or get_seller for seller-focused information.

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