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

Annotations already establish the tool as read-only, idempotent, and non-destructive. The description adds some behavioral context by revealing the nearest-ZIP-centroid methodology and mentioning demo mode, but it does not clarify accuracy expectations, geographic coverage, or what demo mode actually changes.

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 short and front-loads the core purpose in the first sentence. The second sentence about demo mode earns some space but is vague and could be clearer without adding length.

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?

The tool is simple, but the description omits important operational details: it does not state the return value format, whether non-US coordinates are supported, or what 'Demo mode allows selected sample coordinates' actually means. This creates real ambiguity for an agent deciding whether and how to invoke the tool.

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 input schema fully documents lat and lon, so the description does not need to repeat their definitions. The description adds minimal extra meaning beyond the coordinate types, providing no range, format, or coordinate-system details.

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 action and resource: 'Resolve a timezone' from latitude/longitude. The additional 'nearest ZIP centroid logic' distinguishes it from sibling geo tools like geo_enrich or geo_zip_lookup, making the tool's unique role clear.

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 geo_zip_lookup, geo_city_search, or geo_enrich. The phrase 'Demo mode allows selected sample coordinates' hints at a constraint but does not explain when demo mode applies or when production behavior differs.

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