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

With no annotations, the description carries the full burden. It usefully discloses the pricing tiers, including the contingency and appeal addon treatment, but it does not state whether the quote is binding, whether any record is created, whether authentication is required, or what the response looks like.

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 dense sentence that front-loads the main action and embeds the pricing tiers compactly. Every element is relevant to quoting or understanding the service.

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?

There is no output schema, and the description does not specify the return format or whether the tool returns a single number, a line-item breakdown, or tier eligibility. It also omits the parcel-count thresholds that determine which multi-property tier applies, leaving an important gap for correct use.

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 all three parameters are already documented in the schema. The description adds pricing context for the appeal addon and contingency options, but it does not explain how parcel_count maps to the Small Portfolio or Landlord Bundle tiers, which is the key missing semantic detail.

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 uses a specific verb ('Calculate') and resource ('tiered pricing for single or multi-property official mailing address changes') and scopes it to Hamilton County. Sibling tools like check_portfolio_address_status handle status rather than pricing, so the purpose is distinguishable.

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 the tool should be used when a pricing quote is needed, but it does not explicitly state when to use this versus alternatives such as check_portfolio_address_status or suggest_addresses. There are no exclusions or prerequisites beyond the implied context.

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