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

With no annotations provided, the description carries the full burden. It discloses that the tool works offline and specifies the conversion direction (lat,lon to geohash). It does not detail return format or error handling, but the presence of an output schema mitigates that. The description adds meaningful context beyond the schema.

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, efficient sentence that front-loads the purpose and includes a distinguishing trait (offline). There is no wasted wording; 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 simple conversion tool, the description covers the essential information: input format, output type, and offline behavior. The output schema handles return details. The only minor gap is the lack of explicit coordinate format specification, but the tool's simplicity makes it likely an agent can infer it.

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 coverage is 0% for the 'q' parameter, so the description must compensate. It does so by indicating that q should contain 'lat,lon', which gives the agent a clear expectation of the input format. However, it does not specify the exact coordinate format (e.g., decimal degrees, precision), leaving some ambiguity.

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 a specific transformation: lat,lon -> geohash, with the arrow indicating conversion. It distinguishes from siblings like geocode (address to coordinates) and revgeocode (coordinates to address) by its explicit output format. The 'offline' qualifier adds a key trait.

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 implies usage (when you need to encode coordinates to a geohash) but does not explicitly state when to prefer this over alternatives such as geodist or latlonformat. The 'offline' hint is the only contextual cue, but no exclusions or alternative tool names are mentioned.

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