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

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds valuable context about the actual output payload — full ZIP enrichment including demographics, risk, climate, nearby airport, and hazards. It does not describe behavior on invalid addresses, but given the strong annotation coverage, this is a minor gap.

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?

The description is a single, dense sentence with no filler. It front-loads the action and resource, then packs the key enrichment categories into a parenthetical list. Every word earns its place.

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 tool with a single required parameter, strong annotations, and no nested schemas, the description is complete enough for selection and invocation. It states the input type, the US scope, and the main output categories. The absence of an output schema is partially mitigated by the explicit enrichment list, though exact response structure is not described.

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 schema already states 'Free-form US address: street, city, state, ZIP.' The description only repeats the 'US address' concept and adds no new parameter semantics beyond the schema. A baseline of 3 is appropriate because the schema carries the parameter documentation burden.

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 ('Validate') and resource ('US address'), then clearly lists the enrichment output: demographics, risk, climate, nearest airport, hazards. This distinguishes address_enrich from sibling tools like address_validate and geo_zip_lookup without needing to open schemas.

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?

The 'in one call' phrase and the enumerated enrichment categories give an agent clear context for when this tool is appropriate. It does not explicitly name alternatives or exclusion criteria, such as using address_validate when only validation is needed, but the use case is clearly understandable.

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