get_ad_detail

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

With no annotations, the description carries full burden for behavioral transparency. It only states the function but doesn't disclose any traits like read-only nature, required permissions, rate limits, or error behavior (e.g., if ad_id not found). The description is insufficient for understanding operational implications.

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 a single sentence, immediately stating the tool's core function. It is concise with no extraneous information, and the key data points are listed briefly. Every word contributes to the purpose.

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 retrieval tool with one parameter and an output schema, the description adequately covers what the tool does and what data is returned. It explicitly mentions common fields (description, price, location, images). The presence of an output schema means return values are defined elsewhere. Minor improvement would be to mention that ad_id is required and obtained from search_ads.

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 has one parameter (ad_id) with 0% description coverage. The description does not explain the parameter beyond the schema type and requirement. Although the parameter name is self-explanatory, the description should clarify that it is the unique identifier of the ad (e.g., from Leboncoin). Additional context is missing.

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 verb ('Retourne'), the resource ('détail complet d'une annonce Leboncoin'), and the key fields returned (description, price, location, pictures). It distinguishes from the sibling tool 'search_ads', which likely returns a list of ads rather than full details.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives, such as needing an ad_id retrieved from 'search_ads' first. No prerequisites or limitations are mentioned.

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