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

Annotations already cover the safety profile with readOnlyHint, idempotentHint, and destructiveHint, so the description does not need to restate those. The description adds only that this is a composite 'full' pipeline, but it does not disclose any additional behavioral characteristics such as external calls, required dependencies, or failure modes. There is no contradiction with annotations.

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 a single efficient sentence with no filler or redundancy. It front-loads the action and resource, though it is minimal and could include more scoping guidance without becoming verbose.

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 output schema and parameter schema cover return values and input format, so those are not gaps. However, the description does not explain how this tool fits into the broader quoting flow relative to checkEligibility or getAutoQuotes, leaving the agent to infer ordering and prerequisites.

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?

The only parameter, home_input_json, is fully described in the input schema with required keys and a pointer to the full HomeInput model. The tool description adds no parameter-level detail, but because schema description coverage is 100%, the baseline of 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?

The description clearly identifies the action (run) and the resource (full homeowners insurance quoting pipeline). It is distinguishable from the siblings getAutoQuotes and checkEligibility via the terms 'homeowners' and 'quoting', but 'full pipeline' remains somewhat abstract and does not enumerate what stages are included.

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 provides no explicit guidance on when to use this tool versus checkEligibility or getAutoQuotes. There is no mention of ordering, preconditions, or cases where one of the sibling tools would be more appropriate. Usage context must be inferred entirely from the tool name and sibling list.

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