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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds genuine context by naming the data sources (state revenue department and assessor pages), but says nothing about freshness, coverage gaps, or return format.

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?

A single front-loaded sentence that opens with the jurisdiction scope ('UNITED STATES') before listing the returned facets. No filler, though the trailing comma-list makes it read more like a content spec than a purpose statement.

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 full schema coverage, safety annotations, and no output schema, the description carries the burden of conveying what comes back, and it does so by listing the five facets of property-tax information. It is complete enough to call correctly, with only the appeal-sibling overlap left ambiguous.

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% and the single 'state' parameter is fully documented in the schema, including the accepted name/two-letter-code formats. The description adds no syntax or format detail beyond that, so the baseline 3 is correct.

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 names a specific resource (US state property taxation) and enumerates the exact facets covered: assessed value methodology, effective rates for the main city, homestead exemption, assessment caps, and appeals. This tells an agent what the tool returns without opening a schema. It does not, however, differentiate itself from the sibling property_tax_appeal_us, which its mention of 'how to appeal' overlaps with.

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 explicit when-to-use, when-not-to-use, or alternative-tool guidance. An agent must infer from the sibling list that property_tax_appeal_us handles appeals more deeply, since the description never says so. The facet list implies a lookup use case but gives no routing signal.

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