get_product

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

With no annotations, the description carries the burden of behavioral disclosure. The verb 'obtenir' implies a read-only retrieval, and the listing of fields (price, stock, description, photos) gives some insight into the response content. However, it does not explicitly state safety, error behavior, or format completeness, leaving some gaps.

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, front-loaded sentence that directly communicates the tool's purpose and key details. It contains no superfluous words and is efficiently structured.

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 get-by-ID tool with one parameter and no output schema, the description provides sufficient context by listing the types of details returned. It could be more complete by explicitly stating it operates on a single product by ID, but it is adequate for its 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?

The schema already documents the single parameter 'id' with 'ID du produit' at 100% coverage. The description adds no additional meaning about the parameter, so it earns the baseline score of 3.

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 specifies a clear verb ('obtenir' = get) and resource ('un produit' = a product), and lists the exact details returned (price, stock, description, photos). This distinguishes it from sibling tools like get_product_stock or get_product_prices, which return only specific subsets.

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 when you need all product details, but it does not explicitly mention when to use this tool versus alternatives like get_product_stock or list_products. There is no exclusions or alternative guidance, so it falls short of clear context.

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