create_deposit

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

No annotations are provided, so the description carries full burden. It only states the action without disclosing side effects, prerequisites (e.g., validated quote/order), whether the invoice is created as draft or validated, or what response to expect.

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, concise sentence that directly communicates the tool's purpose. No unnecessary 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?

The description is too sparse for a create operation with 5 parameters and no output schema. It lacks essential context about prerequisites, response format, side effects, and parameter details beyond a vague reference to source and percentage.

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 only 40%. The description adds minimal context (origin_type values are 'devis' or 'commande', deposit_percent is a percentage) but does not explain the remaining parameters (date, payment_terms_id). It fails to fully compensate for the low schema coverage.

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 uses a specific verb ('créer') and resource ('facture d'acompte') and clearly states the source ('depuis un devis ou une commande'). It distinguishes this tool from siblings like create_invoice by specifying it creates deposit invoices from quotes or orders.

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 when to use this tool: when a deposit invoice is needed from a quote or order. It provides clear context but does not explicitly state alternatives or exclusions (e.g., when to use create_invoice instead).

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