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

With no annotations, the description carries the full burden. 'Retrieve' signals a read-only operation and the content categories (roll analytics, multi-cycle growth rates, submarket breakdowns) hint at what comes back, but there is nothing on permissions, cost, result size, or response shape for what is billed as a 'comprehensive' dataset.

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 front-loaded sentence with the county and core data categories up front; the parenthetical lists of years and city names add geographic concreteness at modest cost, though the sentence is dense.

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 only one optional parameter, so the description only needs to convey scope and data types, which it does by naming growth cycles and submarket breakdowns; the lack of any return-format hint is a minor gap given the tool's breadth.

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 coverage is 100% for the single optional submarket parameter, with concrete ID and zip-code examples, so the schema does the heavy lifting. The description's phrase 'submarket breakdowns' only loosely signals the parameter's role and adds no syntax or default behavior.

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 ('Retrieve') and a well-defined resource (Knox County historical assessment roll analytics, growth rates, submarket breakdowns). The county qualifier distinguishes it from the sibling get_hamilton_roll_analytics and the generic get_roll_analytics, 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 'Knox County' scoping; an agent can infer to use this instead of get_hamilton_roll_analytics for Knox data, but the description never states when to prefer it, or when to use the generic get_roll_analytics instead.

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