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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds only that the data is 'historical' and limited to two counties, but says nothing about result volume, pagination, time-span coverage, or what happens for an unsupported county.

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 with no wasted clauses, naming the resource and the scope constraint immediately. Minor redundancy with the schema's county description keeps it from being exemplary.

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 simple, read-only two-optional-parameter tool with 100% schema coverage and full annotations, the description supplies the essential scope. The main remaining gap is that with no output schema, nothing conveys what the 'analytics' payload contains — metrics, time range, or granularity.

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 both parameters are already documented, including the default county value. The description's enumeration of Hamilton/Knox largely repeats the schema; it adds no meaning for the optional 'submarket' parameter (e.g., whether an ID and a zip behave differently).

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 ('Retrieve') and a specific resource ('historical property assessment roll analytics') and scopes it to two named counties. It does not explain how it relates to the sibling county-specific tools (get_hamilton_roll_analytics, get_knox_roll_analytics), leaving the agent to infer that this tool is the parameterized general form.

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 implied through the 'supported counties' constraint, which tells the agent this only applies to Hamilton or Knox. There is no explicit when-to-use/when-not guidance and no mention of the county-specific sibling tools that appear to overlap.

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