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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds useful behavioral detail beyond annotations: it standardizes street/unit/city/state/ZIP and cross-checks ZIP against the geo dataset for state and city consistency. No contradiction exists, though it does not cover error handling or output shape.

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 sentence that front-loads the primary purpose and then adds necessary specifics. There is no redundant text or filler; every clause 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 one-parameter read-only tool, the description sufficiently defines the input form and the underlying validation/standardization process. The absence of an output schema is slightly mitigated by the description's mention of standardized components and ZIP consistency, but it never explicitly states the return value or invalid-address behavior.

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?

The schema already documents the address parameter with 100% coverage, so the baseline is 3. The description reinforces that the address is free-form and lists components, but it adds no syntax examples, format expectations, or canonicalization rules 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?

The description names a specific resource (US address) and specific operations: parse, validate, standardize, and cross-check ZIP consistency. It is clear about what the tool does, but it does not explicitly differentiate from siblings like address_validate_batch or address_enrich, so it stops short of a perfect score.

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 description makes clear this tool is for a single free-form US address needing normalization and validation, which implies appropriate use. It does not explicitly state when to prefer address_enrich or address_validate_batch, so exclusion guidance is missing.

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