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

Annotations already declare idempotent and non-destructive behavior; the description adds meaningful behavioral detail: asynchronous execution, returning an operation ID, spending and rights scope from the quote, and the removal distinction. It goes beyond annotation fields but does not cover failure modes or what happens on invalid quotes.

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?

Four short sentences, each carrying distinct information: the action, quote scope, follow-up polling, and a caveat about removal. The primary verb and resource are front-loaded, and there is no filler.

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 two-parameter async trigger with no output schema, the description covers what an agent needs to invoke it correctly: preconditions, the operation-ID return value, the polling route, idempotency via the key, and what the action is not. Sibling tool names fill the remaining selection context.

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 0%, so the description must compensate. It explains quote_id well by saying the quote bounds spending and contains rights scope/input. However, idempotency_key is left to its name and the idempotentHint annotation, so parameter compensation is incomplete.

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?

States a concrete action ('execute') on a specific resource ('pre-approved investigate quote') and clarifies async behavior. It differentiates from siblings like create_quote (producing the quote) and get_operation (polling the result), and the 'distinct from removal' caveat separates it from takedown/removal tools.

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?

Implies use only after a quote is pre-approved, explicitly instructs to poll get_operation, and warns that submission is not removal, steering agents away from removal tools. However, it does not explicitly name prerequisites like create_quote or enumerate when not to use it compared with other investigation-related siblings.

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