convert_quote_to_invoice

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

With no annotations provided, the description carries full responsibility for disclosing side effects, prerequisites, and post-conditions. It does not mention what happens to the quote after conversion, whether the operation is reversible, or any required permissions, leaving significant behavioral ambiguity.

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, efficient sentence with no fluff or repetition. It is appropriately short but could have included additional context in the same space, so it is not a perfect 5.

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?

This is a state-changing conversion tool, yet the description provides minimal context. It does not explain the relationship between the quote and the resulting invoice, whether the quote status changes, or what the tool returns. Given no output schema and no annotations, the description is inadequate for an agent to fully understand the tool's impact.

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 provides a complete description for the single parameter ('The quote UUID to convert'), and the description does not add additional parameter semantics beyond reusing the term 'accepted quote'. Schema coverage is 100%, so the baseline of 3 applies.

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 (convert) and the resources involved (accepted quote to draft invoice). It uses a specific verb and distinguishes this tool from siblings like create_invoice or update_quote_status, making the purpose unmistakable.

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 phrase 'accepted quote' implies the tool is only appropriate for quotes in the accepted state, providing context for when to use it. However, it does not explicitly state when not to use it or mention alternatives, so it stops short of full guidance.

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