Détails d'un(e) produit

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

The description states the tool is read-only ('Récupère'), consistent with annotations (readOnlyHint: true). However, it does not describe behavior on missing IDs or permission issues. Annotations already cover idempotency and destructiveness, so description adds minimal extra transparency.

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 extremely concise: two sentences plus an Args/Returns block. It front-loads the main purpose and includes all key information without any wasted words.

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?

Given the tool's simplicity (2 parameters, no output schema), the description adequately covers what it does and returns. However, it lacks details like error handling or rate limits. With good annotations, this is sufficient but not fully comprehensive.

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%, with both parameters described in the schema. The description repeats the parameter names and lists possible tabs, but the schema already provides this enumeration. Thus, the description adds no significant semantic meaning beyond 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 verb 'Récupère' and the resource 'produit par son ID', specifying detailed information retrieval. It distinguishes from sibling tools like boond_products_search, which is for searching, not getting 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 usage when you have a product ID and optionally want a specific tab, but it does not explicitly state when to use this tool vs. alternatives like search. No exclusions or alternative tool references are provided.

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