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

The annotations already declare this as a safe, read-only, idempotent, closed-world operation. Beyond that, the description explains the calculation model, the $5 rounding, the default behavior for every optional input, and the exact return contents including price range, hours, per-square-foot cross-check, math, and an adjustability link.

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 front-loaded with the core purpose, then covers return values and defaults in three dense but purposeful sentences. The first sentence is long and complex, but no sentence feels wasted.

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 properly explains what the tool returns. It also covers default behavior, calculation logic, and optional inputs, making it complete for a read-only estimation tool of this complexity.

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%, so the schema already documents each parameter's enums, defaults, ranges, and add-on prices. The description adds value by describing how parameters interact in the calculation: size and square footage determine time on site, which is multiplied by frequency and hourly rate, then adjusted for market and add-ons.

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: it prices one residential house cleaning visit using a defined calculation. It is immediately distinguishable from the unrelated sibling tools, which cover sales tax, free tool lookup, and gas leaf blower rules.

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 implies usage by saying it prices one residential house cleaning visit, but it does not explicitly state when to use it or when not to use it, such as for commercial cleanings or multi-visit planning. No alternatives exist among the siblings, so the implied context is adequate but not fully expressed.

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