create_invoice_from_quote

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

The description adds no behavioral context beyond what the annotations already provide (readOnlyHint=false, destructiveHint=false). It doesn't disclose side effects like whether the quote is marked as invoiced, or any permission requirements. With such a minimal description, the agent learns nothing new about the tool's behavior.

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 extremely brief, essentially restating the tool name. While there is no wasted text, it also provides no additional structure or detail, making it minimally acceptable but not exemplary.

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 tool that creates an invoice from a quote, the description is incomplete. It doesn't explain the relationship with the quote, any prerequisites (e.g., quote must be in a certain state), or the resulting invoice behavior. The openWorldHint and lack of output schema increase the need for richer context, which is absent.

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 already fully describes both parameters (quote_id and positions), including a note about omitting positions to copy all from the source. Since schema coverage is 100%, the description doesn't need to add parameter details, and it correctly doesn't.

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 ('create') and the resource ('invoice from quote'), making the tool's purpose unambiguous. It also distinguishes itself from sibling tools like create_invoice and create_invoice_from_order by specifying the source as a quote.

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 guidance is given on when to use this tool versus alternatives such as create_invoice or create_invoice_from_order. The description fails to mention any context, prerequisites, or exclusions that would help an agent choose correctly.

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