Update Quote

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

Annotations indicate mutation, non-destructive, idempotent, and open-world. The description adds partial update semantics and a specific read-only constraint, going beyond annotations.

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, front-loaded with purpose, no extraneous text. 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?

For an update tool with many parameters and custom fields, the description covers key points (ID, partial update, read-only field). No output schema is needed. Slightly more detail on custom fields could help, but schema handles it.

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 coverage is 100%, so baseline 3. Description adds 'only provided fields' context but no per-parameter details beyond schema descriptions. The read-only note is about a non-schema field.

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 tool updates an existing quote by ID, distinguishing it from create/get/list/delete. It specifies partial update behavior and notes a read-only field.

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 explains that only provided fields are changed and highlights the QuoteNumber as read-only. While it doesn't explicitly compare to create or delete, the update intent is clear.

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