Approve a draft quote (internal)

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

Discloses that the quote transitions to a 'live SENT version' and that prior versions are 'superseded', adding context beyond annotations. No contradiction with annotations though destructiveHint is false; 'superseded' is not necessarily destructive.

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?

Two sentences with no redundant information. Purpose is front-loaded and every sentence adds value.

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?

Given no output schema, the description explains the result (becomes live SENT version) and addresses prior versions. Also clarifies what it does not do, making the tool's behavior fully understood.

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?

With 100% schema coverage, baseline is 3. The description adds value by explaining the confirmation workflow ('State the quote and total, get an explicit yes, then call with confirmed: true'), which is not in the schema.

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?

Clearly states the verb 'Approve' and the resource 'DRAFT quote', explains the effect ('becomes the live SENT version; prior versions are superseded'), and distinguishes from siblings like setell_send_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?

Explicitly tells when not to use ('Does NOT email the customer') and provides alternative tools ('use setell_compose_quote + setell_send_quote for delivery'). Also gives a step-by-step workflow for calling the tool.

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