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

The description goes beyond the generic annotations by revealing that the tool is free, never bookable, and limited to quote scope. This is valuable behavioral disclosure that helps the agent understand the tool will not create a booking or commit the user.

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?

Two short sentences, both purposeful and front-loaded. The first states the core function; the second adds scope and behavioral constraints without any filler or redundancy.

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?

For a tool with a fully described nested schema, the description provides the essential role and constraints: estimate range, quote scope, free, and never bookable. It does not describe the exact output format, but 'estimate range' conveys the primary return concept, and the schema covers all parameter semantics.

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 detailed parameter descriptions already present in the input schema. The description's mention of 'home size + addresses' loosely maps to parameters but adds no new parameter-level meaning, so the baseline score of 3 applies.

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 creates an instant estimate range from home size and addresses, with 'Scope: quote' and 'never bookable' helping separate it from booking-oriented siblings. It is specific about the resource (estimate range) and the inputs, though it does not name a sibling explicitly.

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?

'Free; never bookable. Scope: quote' implies this tool is for the quick quote stage rather than for booking or job creation, which gives the agent useful context. However, it does not explicitly name alternatives like request_booking or quote_inventory, nor state when not to use this tool.

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