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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered. The description adds genuine content beyond that by disclosing which cycles are available (2017, 2021, 2025) and that submarket breakdowns are produced, but says nothing about result volume, pagination, or what happens when no submarket is supplied.

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?

One sentence, front-loaded with the verb and resource, with the scope qualifier and metric list trailing. No filler, though the parenthetical place-name list is slightly bulky.

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 read-only analytics tool with one optional filter and no output schema, the description conveys enough about what comes back (historical roll data, multi-cycle growth rates, submarket breakdowns). The main residual gap is how aggregate behavior differs when the submarket parameter is omitted.

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?

With a single optional parameter at 100% schema description coverage including concrete example values (zip codes and submarket slugs), the schema already carries the semantics. The description only reinforces that submarket drives 'neighborhood metrics,' adding little beyond the schema.

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?

States a specific verb+resource (retrieve historical property assessment roll analytics) scoped to Knox County, TN, and enumerates the metrics returned (multi-cycle growth rates, submarket breakdowns). This clearly separates it from the generic get_roll_analytics and the county-specific get_hamilton_roll_analytics siblings, though it never names those alternatives directly.

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?

Usage is only implied through the geographic scope (Knox County, Farragut, Bearden). There is no explicit when-to-use statement, no condition distinguishing it from get_roll_analytics or get_hamilton_roll_analytics, and no prerequisites or exclusions.

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