sales_confirm_order

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

With no annotations provided, the description carries full burden but only states the conversion action without disclosing behavioral traits. It doesn't mention if this is a mutation, requires specific permissions, affects other data, or has side effects like notifications or status changes.

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 zero waste, front-loading the core action and purpose appropriately.

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 mutation tool with no annotations and no output schema, the description is incomplete. It lacks details on behavioral aspects, return values, error conditions, or how it integrates with the sales process, leaving significant gaps for 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?

Schema description coverage is 100%, so the input schema already documents the order_id parameter. The description doesn't add meaning beyond the schema, such as clarifying what constitutes a valid order_id or how it relates to quotations.

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 ('confirm') and resource ('quotation'), specifying that it converts to a sales order. However, it doesn't explicitly differentiate from sibling tools like sales_create_order or sales_list_orders, which handle different aspects of sales 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 usage for converting quotations to sales orders but provides no guidance on when to use this versus alternatives like sales_create_order or prerequisites. There's no mention of when-not-to-use scenarios or explicit alternatives.

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