batch_reverse_geocode

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

Discloses that results are in the same order as input, which is important behavioral information. No annotations are provided, so the description bears full burden. It could mention error handling or rate limits, but the disclosed behavior is sufficient for most use cases.

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?

Extremely concise: three sentences, a sample return line, and use cases. No unnecessary words. Front-loaded with action and context.

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 provides complete context: purpose, usage guidelines, return format, and examples. The sibling tools are clearly differentiated.

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 100%, so the description adds no extra meaning beyond what the schema already provides. The description repeats the structure but does not clarify edge cases or formatting requirements.

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 performs reverse geocoding for multiple coordinates in a single API request. It distinguishes from the sibling tool 'reverse_geocode' by explicitly noting its batch capability, and from 'batch_geocode' by specifying reverse geocoding.

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?

Provides explicit guidance: 'Always use batch_reverse_geocode for 2+ coordinates. Never loop reverse_geocode calls.' Also lists specific use cases (enriching GPS exports, converting datasets).

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