create_supplier_order

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

No annotations are provided, so the description carries full transparency. It discloses the mutating action (create) and goes beyond that by detailing required behavior: check current stock, present a full summary, and request confirmation. This adds valuable context, though it does not cover permissions, reversibility, or post-creation effects.

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?

Three sentences, each earning its place: the action, the usage trigger, and the essential pre-flight checks. No redundancy, well front-loaded with the main 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 creation tool with no output schema and no annotations, the description provides the core action, when to use, and critical workflow steps (check stock, confirm). It omits the return value or system effects, but the essential guidance is solid and sufficient for an agent to invoke correctly.

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 description coverage is 100%, with each parameter already well-described (e.g., supplier_name as 'Nom exact du fournisseur dans ERPNext', rate as 'Prix d'achat optionnel'). The description adds no parameter-level detail beyond the schema, so baseline 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 clearly states 'Créer une commande fournisseur dans ERPNext' (create a supplier order) and further explains it is for ordering products from a supplier. This specific verb+resource combination, along with the supplier context, distinguishes it from siblings like create_sale or receive_stock.

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?

It explicitly says to use when the user wants to order products from a supplier, and provides a mandatory pre-check ('Toujours vérifier le stock actuel') and confirmation step. While it does not mention when not to use or name alternatives, the context is clear and actionable.

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