Services accept quote

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

The description goes far beyond annotations. It reveals that this operation charges immediately, shares rails with goods purchases, can return a confirmation_required kickback with a token, requires re-acceptance after principal sign-off, and holds funds in escrow until deliverable acceptance. This is rich behavioral disclosure that the annotations (only readOnlyHint=false, etc.) do not provide. No contradiction with 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?

The description is two sentences but packs substantial information without redundancy. It front-loads the primary action, then explains the special kickback scenario and escrow behavior. Every clause adds value, and there is no fluff. The structure is efficient and easy to parse.

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 with 5 parameters, no output schema, and complex behavior (kickbacks, escrow, delegation), the description covers the essential flow: immediate charge, potential confirmation_required retry, and escrow holding. It doesn't detail return values, but with no output schema, that is not required. The description is sufficiently complete for an agent to call it correctly in most scenarios.

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 schema has 100% coverage for all 5 parameters with descriptive text. The description adds semantic context by explaining the relationship between confirmation_token and acknowledged_confirmation, and how payment_method_id is optional with a fallback to envelope-bound card. This goes beyond the schema's individual parameter descriptions, enhancing the agent's understanding of the flow.

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 states a specific action ('Accept a submitted quote and charge immediately') with a clear resource and effect. It distinguishes from sibling tools like services_purchase (which likely handles direct purchase) and services_submit_quote (which is for providers). The verb 'accept' plus the immediate charge clearly differentiates it from reject/counter flows.

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 the primary use case: accepting a quote and initiating payment. It explicitly describes the retry flow when a confirmation_required kickback occurs, telling the agent to re-accept with acknowledged_confirmation and the token. It doesn't explicitly state alternatives, but the context (services workflow) and the mention of 'delegation caps' and 'payment-envelope rails' give enough guidance for when to use this vs. other services tools.

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