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

Annotation Contradiction: readOnlyHint=true indicates the tool does not modify state, but the description says 'the request is still registered and a quote_id returned so licensed agents can quote it,' which implies a persistent side effect. This directly contradicts the read-only annotation and is a serious inconsistency for an agent relying on the tool's safety profile.

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?

The description is four sentences, front-loaded with the main purpose, and every sentence adds useful information: what it returns, what it does not require, unlicensed fallback behavior, and server behavior on missing facts. There is no repetition or fluff.

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?

The description covers purpose, PII exclusions, unlicensed fallback, and missing-facts behavior. However, there is no output schema, and the successful licensed-path response format is only described as 'prices' without details. With 10 parameters and a contradictory read-only annotation, the description is not fully sufficient for an agent to confidently predict all invocation outcomes.

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 only 20%, and the description does not compensate. It explains that only rating facts are needed and lists excluded PII, but it does not clarify the meaning of fields like annual_mileage, violations_3yr, years_licensed, prior_continuous, or vehicle_make_model beyond their names. The 'server asks for exactly what it needs' note reduces some upfront burden, but the description still leaves most parameter semantics unexplained.

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 clearly states the tool's verb and resource: 'Return indicative auto insurance prices from multiple carriers.' It also clarifies the licensing boundary and the fallback of returning a quote_id, which distinguishes this from simple quote retrieval. This is specific enough for an agent to understand what the tool does and how it differs from sibling tools like request_agent_contact.

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 description gives clear context: use this for indicative prices using only rating facts, with no PII required. It also explains the behavior when the entity is not licensed. However, it does not explicitly name sibling alternatives or state when not to use this tool, so the agent must infer the boundary from context.

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