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

No annotations are provided, so the description carries the full burden. It mentions the maximum of 200 ZIP codes, a useful constraint, but does not disclose behavior for invalid ZIPs, error handling, or the exact structure of the response.

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 two concise sentences. The first states the operation, the second gives usage guidance. Every word is necessary with no filler.

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 simple tool with one parameter and no output schema, the description covers the essential purpose, input constraints, and usage scenario. It could mention the output format (e.g., returns lat/lng pairs), but is largely complete.

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?

With 0% schema description coverage, the description adds meaning by specifying the parameter accepts ZIP codes and has a maximum count of 200. This compensates well for the lack of schema detail.

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 verb 'Get' and the resource 'latitude/longitude centroid for ZIP codes', and specifies the scope 'one or more ZIP codes (max 200)'. It distinguishes from siblings like get_zip_profile (which returns more data) and reverse_geocode (which maps coordinates to ZIPs).

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 provides a clear usage context: 'Use when you need map coordinates for a set of ZIPs.' While it doesn't explicitly exclude other tools, this guidance effectively directs the agent to this tool for centroid retrieval.

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