creer_devis_brouillon

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

With no annotations, the description carries the full burden. It discloses the permission required (devis:write), the draft state, and the non-sending behavior, which are key side-effects. However, it doesn't mention return values or error handling, leaving some behavioral aspects undisclosed.

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 only two sentences, front-loaded with the main action. Every sentence adds value: the first defines the operation and permission, the second details line structure and the non-sending behavior. No redundancy.

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 annotations or output schema, this description covers the core context: purpose, permission, line item schema, and post-creation behavior. Missing details like return format or parameter constraints are minor gaps given the simple create operation.

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 0%, so the description must compensate. It specifies the structure of the 'lignes' array items ({designation, quantite, prix_unitaire_ht, taux_tva}), which is essential. However, it does not explain 'client_id', 'chantier_id', or 'objet', though some are inferred by their names.

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 tool's function: 'Crée un devis en BROUILLON' (creates a draft quote). The verb+resource+state is specific, and it distinguishes itself from sibling tools like factures and clients by focusing on devis 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 explains that the devis is never sent automatically, indicating the tool is for drafts only and the user must later review/send it in VoxFactura. This provides clear usage context, though it doesn't explicitly mention alternative tools for sending or managing quotes.

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