invoice_from_quote

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

Without annotations, the description must fully disclose behavioral traits. It states a create operation but omits details: Does it update the quote status? What if the quote already has an invoice? Are any checks performed? The description provides minimal insight beyond the basic action.

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 very short (one phrase) and front-loaded with the key action and resource. However, it is not a complete sentence and could benefit from slightly more structure without losing conciseness.

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 single-parameter tool with no output schema, the description could be complete, but it lacks critical context such as what happens after creation (e.g., returns invoice ID), whether the source quote is modified, or any error conditions. The description is too minimal to fully guide an AI agent.

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?

The input schema describes 'quote_id' with only '(path parameter)'. The description does not add any meaning beyond what the schema provides. For instance, it could explain that this is the ID of the quote to convert, but it does not. Schema coverage is 100% but the schema itself is sparse.

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 action 'Créer une facture' (create an invoice) and the source 'à partir d'un devis' (from a quote). It distinguishes itself from siblings like 'create_invoice' (which creates an invoice from scratch) and 'accept_quote' (which does not create an invoice).

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 guidelines on when to use this tool vs alternatives. It does not mention prerequisites (e.g., quote must exist and be accepted) or typical scenarios. The description lacks context for an AI agent to decide between this and related tools like 'create_invoice'.

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