batch_geocode

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the batch limit but omits critical behaviors: return format, error handling for partial failures, ordering of results, quota impact, or rate limits. An agent cannot anticipate what happens when some addresses fail.

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?

One clear, front-loaded sentence with zero redundancy. The purpose and limit are stated immediately with no wasted words.

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?

As a batch tool with no output schema and no annotations, the description is too sparse. It does not mention the return structure (e.g., array of geocoded results in input order), failure behavior, or any usage constraints beyond the count. An agent lacks enough information to handle errors or interpret results correctly.

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 address object fields and maxItems are already documented. The description adds the word 'batch' but that is implied by the tool name and sibling context; it provides no new semantics beyond the schema. Baseline of 3 is appropriate.

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?

States the specific verb 'Geocode', the resource 'multiple addresses', and the batch nature with a limit. Clearly distinguishes from siblings like geocode (single address) and reverse_geocode (reverse direction) without needing to open schemas.

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 clear context that this is for batch requests, implying use when multiple addresses are needed. Does not explicitly state exclusions or name alternatives (e.g., 'use geocode for single addresses'), so it stops short of a 5.

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