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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description goes beyond that by disclosing polling fallback behavior, the offered/declined status branches, and that 'creating the job accepts those terms' — genuine behavioral context. It omits auth/token handling details.

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, front-loaded with the core action, and each subsequent sentence carries distinct behavioral value (polling fallback, offered-status fields, declined handling). 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?

With no output schema, the description must carry return-value burden and does partially describe what to inspect (service fee, expense authority, expiry, decline reason). But it leaves the two required parameters unexplained and does not enumerate the full status set or error cases, leaving visible gaps.

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% and the description neither mentions nor explains quote_id or quote_token. With two required parameters at zero coverage, the description should compensate but adds nothing about parameter meaning or usage.

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 ('Retrieve a human-reviewed quote'), which is clearly distinct from human_request_quote's create-quote behavior. It stops short of naming a sibling tool explicitly, but the resource is unambiguous.

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 gives real usage context: polling is always available as a fallback even when callback_url was supplied, and it tells the agent what to do at status=offered vs. declined. It does not, however, name an alternative tool or state an exclusion condition explicitly.

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