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

With no annotations provided, the description carries the full burden of disclosing side effects, required permissions, pipeline side effects, or whether the operation is read-only. 'Run the full ... pipeline' hints at a multi-step process but does not reveal whether it mutates data, calls external services, needs prior eligibility checks, or what happens on failure. The behavioral surface is essentially undisclosed.

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 concise sentence with no filler or repetition, and the core action is front-loaded. It is appropriately brief for a tool with one well-documented parameter. It lacks nuance, but from a purely structural and conciseness standpoint it is efficient.

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?

Although the output schema exists and the sole parameter is well documented, the description is too thin for a pipeline-style tool. It does not explain what 'full pipeline' means, what inputs the caller must have ready, whether eligibility is a prerequisite, or any side effects. Given no annotations, the description alone leaves significant gaps for an agent deciding whether and how to invoke this tool.

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 coverage is 100% and the schema itself gives a detailed description of home_input_json, including required keys and a pointer to engine/validator.py. The tool description adds no parameter-level meaning beyond the schema, so the baseline of 3 is appropriate since the schema already does the heavy lifting.

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 clear action ('Run') and a specific resource ('the full homeowners insurance quoting pipeline'), which distinguishes it from the auto quoting sibling and implies a broader scope than checkEligibility. However, it does not explicitly name alternatives or explain what 'full pipeline' entails, so it stops short of full sibling differentiation.

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?

There is no guidance on when to use this tool versus the siblings checkEligibility or getAutoQuotes. The description implies it is for full homeowners quotes, but it never states exclusions, prerequisites, or alternative conditions. An agent must infer the intended use case from the tool name alone.

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