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

Annotations already declare readOnly, idempotent, openWorld, non-destructive, so the description isn't carrying the safety burden. It still adds real behavioral value: free, no account, nothing stored, and the guarantee that misses come back with a reason rather than a blank. It doesn't discuss rate limits or result size, which keeps it from a 5.

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?

Front-loaded with the core mapping and dense with useful detail; the two example invocations anchor usage cheaply. The middle sentence is long and slightly run-on, but every clause carries information, so it stays efficient.

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?

An output schema exists, so the description need not enumerate return structure, and it correctly focuses on geography, coverage scope, and miss-handling behavior. For a single-parameter lookup with rich annotations, nothing an agent needs is missing.

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?

Only one parameter, and schema coverage is 100% — the schema already explains to include the city because 'Grand Ave' exists in several of them. The description adds no additional syntax or format guidance for the address field, so baseline 3 applies.

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 input (one address in the Minneapolis–St. Paul metro) and an enumerated set of outputs (land use, build year, assessed value, last sale, MPCA contamination/storage-tank file, adjoining parcels with owner counts). The scope is narrow and unmistakable, so an agent can distinguish it from a general records tool.

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?

Explicitly says to use it 'the moment an address comes up' and names the follow-on alternative, twin_cities_records, for the surrounding market. Trigger condition and routing are both stated, not inferred.

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