Bons de commande d'une société

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description only adds 'Récupère', which is consistent but does not provide additional behavioral context such as error handling, empty results, or API behavior beyond what annotations already convey.

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?

Extremely concise: two sentences plus Args section, front-loaded with the purpose. Every sentence is necessary and no redundant 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?

Adequate for a simple retrieval tool with one parameter and no output schema. It specifies the return as a list, but lacks details on pagination, filtering, or error cases. The context is sufficient but not thorough.

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 a description for the id parameter. The tool description adds that the ID is for the company ('ID de la société'), which is slightly more specific than the schema's 'Identifiant unique de l'entité BoondManager'. This minimal addition does not significantly enhance understanding.

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 it retrieves purchase orders for a company, using specific verb 'Récupère' and resource 'bons de commande'. The title also specifies 'd'une société'. This differentiates it from sibling tools like boond_orders_get (single order) and boond_orders_search (search orders) by explicitly linking to a company.

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 guidance on when to use this tool versus alternatives like boond_orders_search. It only states the input and output, lacking context on scenarios or exclusions. The agent must infer usage from the name and siblings.

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