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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond these by specifying it validates deliverability and returns standardized address components, county, coordinates, and residential/commercial classification. It does not contradict annotations.

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 front-loaded sentence stating the core purpose and returns, followed by a concrete example. There is no fluff or redundant filler; every part 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 no output schema, the description gives a good list of return data, and the schema covers all parameters. It could mention limitations or expected behavior on invalid addresses, but the combination of schema, annotations, and description is largely sufficient for an agent to call the tool correctly.

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 the baseline is 3. The description's example reinforces the parameter structure but does not add meaning beyond what the schema already provides for street, city, state, zipcode, and _apiKey.

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 clearly states the tool verifies and standardizes a US address, listing specific return values like USPS-standardized address, county, lat/lon, ZIP+4, and residential/commercial indicator. It uses a specific verb and resource, but it does not explicitly distinguish this from the sibling smarty_property_enrichment, so it stops short of a 5.

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?

There is no guidance about when to use this tool versus alternatives such as smarty_property_enrichment, nor any explicit exclusions or conditions. The description implies it is for US address verification, but it does not provide decision criteria or mention when not to use it.

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