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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Non-mutating'. It adds one genuinely useful piece of context: the underlying transport is POST /v1/us_zip_lookups, which stops an agent from misreading a POST as a write operation. Beyond that it says nothing about rate limits, auth, or error behaviour for invalid ZIPs.

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?

Three short sentences with zero padding, and the core behaviour is front-loaded before the non-mutation note and endpoint reference. Every clause carries information.

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?

With no output schema, the description steps in to say what comes back (cities and state), which is the key return-value fact for this tool. It is slightly thin on edge cases, such as invalid ZIPs or ZIPs mapping to multiple cities, but it is adequate for a one-parameter lookup.

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?

There is a single parameter with 100% schema description coverage ('A 5-digit US ZIP code, e.g. 94107'), so the schema already carries the semantics. The description adds nothing about the ZIP format or validation beyond what the schema provides, which is the expected baseline here.

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 states a specific verb and resource: return the cities and state associated with a US ZIP code. That is unambiguous and instantly readable. It does not, however, distinguish itself from near-neighbours such as lob_us_autocomplete or lob_verify_us_address, which an agent may confuse for this lookup.

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 when-to-use or when-not-to-use guidance and no mention of the sibling tools (lob_us_autocomplete, lob_verify_us_address) that overlap with this one. The agent must infer the use case from the name alone, which is the bare minimum rather than explicit routing.

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