geocode

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

Discloses support for street-level resolution and proximity biasing, which are relevant behavioral traits. However, with no annotations, the description could detail data freshness, error behavior, or response format, which are missing.

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?

Two concise sentences front-loading purpose and usage. No wasted words, but could be slightly more structured with separate sections.

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, and the description only vaguely mentions 'coordinates and structured location results'. For a geocoding tool, missing details on result fields, coordinate format, or multiple matches makes it incomplete given the complexity.

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 is an empty object with no parameters. The description mentions the input is text but does not clarify how to provide it (e.g., query parameter or request body). Schema coverage is 100% only because there are no parameters, but the description fails to specify the input structure.

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 tool converts addresses, place names, streets, or intersections into coordinates and structured location results. It distinguishes from reverse_geocode by specifying direction, and from batch_geocode by indicating single input.

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 states when to use: when input is text and coordinates are needed before routing, weather, or search. Does not list when not to use or mention alternatives like batch_geocode for multiple queries, but provides useful context.

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