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

Annotations already declare non-destructive, closed-world, non-read-only behavior. The description adds useful scope context by stating that no contact details or project description are accepted or sent, but it does not explain what the prepare step actually creates, how long the handoff remains valid, or why an idempotency key is required despite idempotentHint=false.

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 short sentences with no filler. The core action is front-loaded, and the second sentence adds a meaningful constraint rather than restating the title.

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?

There is no output schema, and the description only briefly gestures at the return value ('show exactly where the shopper will continue'). With two required parameters at 0% schema coverage and no explanation of idempotency behavior, the definition is not complete enough for an agent to call it confidently.

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% for both parameters. The description only vaguely implies that business_id identifies the 'verified quote destination' and says nothing about idempotency_key, so it does not compensate for the undocumented 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?

The description states a specific verb and resource: prepare a handoff to a verified quote destination. It is clear what the tool does, but it does not explicitly distinguish itself from the sibling confirm_quote_handoff, leaving the prepare-vs-confirm boundary to inference.

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 phrase 'currently verified quote destination' implies a precondition, but the description never states when to use this tool versus confirm_quote_handoff or what to do if no verified destination exists. Usage is implied rather than guided.

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