Verify US Address

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint=false. Description adds important operational context: requires STHAN_API_KEY, counts toward rate limit, mentions free tier, and describes error responses. No contradiction with 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?

Front-loaded with main purpose, then provides details in a logical order. Efficient use of sentences, though slightly verbose in explaining return fields that could be in output schema.

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?

No output schema, but description thoroughly explains return values (standardized address, ZIP+4, county, deliverability status, dpvConfirmation code with meanings). Addresses key considerations: API key, rate limits, error handling.

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 has 100% coverage for the single parameter 'address' with a clear description. The tool description adds examples of input formats, which is helpful but not substantial beyond 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?

Clearly states it verifies US street addresses for deliverability, lists specific return fields (standardized address, ZIP+4, county, deliverability status, dpvConfirmation code), and distinguishes from siblings like sthan_geocode and sthan_parse_address.

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 when to use (confirm address, clean data, before shipping) and when not to (non-US, get map coordinates, split address without checking), and includes explicit alternatives (sthan_geocode, sthan_parse_address).

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