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

Goes well beyond the annotations: it discloses the async/long-running nature, timing windows (30-90s for first prices, 2-10 min to reach verified rates), and the semantic difference between preliminary and bindable figures. This is exactly the context annotations (readOnlyHint=false, openWorldHint=true) cannot convey. The unchanged-vs-changed re-call rule slightly softens idempotentHint=false, but it describes genuine side-effect behavior, so it is not a contradiction.

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?

Front-loaded with the core action and only mildly verbose across five sentences. The timing and estimate-vs-verified detail earns its place, though the prose could be tightened slightly.

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?

Given an output schema exists, the description needn't explain return values, and it still supplies the async lifecycle an agent needs to avoid mis-calling. Combined with annotations covering the safety profile and a fully documented schema, nothing material is missing.

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 100%, with quote_id and max_options fully documented in the schema, so the description carries no parameter burden. It adds no syntax or constraint detail (e.g., it never mentions max_options), which matches the baseline 3 when the schema does the work.

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?

Names a specific verb and resource ('Starts rating with Libertas's panel of A-rated carriers') and describes what the call yields (priced options that move from 'estimate' to 'verified'). It is clearly distinguishable from siblings like check_quote_status and start_quote, which it names or implies.

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?

Explicitly routes the agent: 'Follow progress with check_quote_status every turn or two,' and defines the re-call contract ('unchanged details returns the run already in progress; changed details start a fresh run'). Both the alternative tool and the when-to-call-again condition are stated.

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