Créer un(e) bon de commande

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

Annotations provide no safety profile (all false), so the description carries full burden. It only states 'creates' and return behavior, but doesn't disclose idempotency, permissions, or potential side effects beyond creation. Minimal value added.

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?

Two short sentences, front-loaded with purpose. No unnecessary words, efficient and clear.

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 create tool with 11 optional parameters and output schema, the description is minimal. It doesn't explain how to construct a valid order, required fields in practice, or the structure of the 'schedules' array. While output schema exists, missing guidance on creating a complete object.

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%, so baseline is 3. The description adds no extra meaning beyond parameter names and types. It doesn't explain relationships or constraints between parameters (e.g., schedules structure).

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 creates a new purchase order in BoondManager and returns the created data with ID. It distinguishes from sibling tools (get, search, update, delete) by focusing on creation.

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 use for creating a new order, but lacks explicit guidance on when to use this tool versus alternatives like update (for existing orders) or prerequisites. No exclusions or context is provided.

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