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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, but the description adds genuinely useful outcome context: this is 'not a bound policy and no price is promised', a licensed agent follows up, and consent must be obtained before contacting. That clarifies the real-world consequence of the call beyond the hints.

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?

Three tight sentences with no filler, front-loaded on the action and immediately followed by the collection checklist and the expectation-setting caveat. Every sentence carries information.

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 8-parameter write-ish tool with no output schema, the description covers the flow, the consent prerequisite, and the expected outcome, which is enough to call it correctly. Minor gaps remain: it does not say whether email or phone is required when the other is absent, nor what a failure/decline looks like.

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 75%, so the schema already documents most parameters including the line enum and the consent semantics. The description restates the same fields ('name, an email or phone, the line, the state and what they need covered') but adds no format or edge-case detail; baseline 3 is appropriate.

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 specific verb and resource ('Send a quote request to CalRisk Insurance Center's licensed staff'), which is clearly distinct from a generic info lookup. It does not explicitly contrast itself with the sibling start_online_quote, so an agent must infer that this is the human/agency route versus a self-serve route.

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?

It implies usage context ('get their OK before calling', agent replies) and lists the information to collect, which functions as an implicit precondition checklist. However, it never states when to prefer this over start_online_quote or check_appetite, and no explicit when-not guidance is given.

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