batch_geocode

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

The description discloses key behaviors: sequential processing (rate limit respect) and that individual failures do not abort the batch. It also provides retry advice. No annotations exist, so the description carries the full burden. A minor point is that it does not mention any potential performance or timeout implications, but overall it is transparent.

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 well-structured with sections (Args, Returns, CRITICAL guidance) and is front-loaded with the main purpose. It effectively communicates essential information, though the retry guidance could be integrated more concisely. Still, every sentence serves a purpose.

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?

Given no annotations and no output schema, the description sufficiently covers the tool's behavior, parameters, and error handling. It also provides clear retry logic. It is complete enough for an agent to use correctly, though it could mention expected return format in more detail.

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?

Although the schema has 0% description coverage, the description adds meaning for all three parameters: 'queries' explained as a JSON array of place names (with example), 'limit' as max results per query, and 'output_mode' as 'json' or 'text'. This significantly clarifies usage, though there is a slight inconsistency: schema type for queries is 'string' but description says 'JSON array', which could cause confusion.

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's purpose: 'Geocode multiple place names in one call.' It distinguishes from siblings by emphasizing batch processing and mentions sequential execution and rate limits, making the purpose specific and unambiguous.

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 provides explicit guidance on when to use this tool, including sequential processing to respect rate limits. It includes critical retry guidance: if a query fails, use the single geocode tool with simplified names, directly addressing failure scenarios and alternatives.

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