batch_geocode_locations

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

No annotations are provided, so the description carries the behavioral burden. It discloses the key behavioral traits: 10,000 address cap, locations-only restriction, input format options, and precedence rules ('Takes precedence over the addresses array'). It also enumerates the return CSV columns. Missing details on error handling or rate limits, but substantial for an unannotated tool.

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 dense yet well-structured, front-loading the core action and limits, then detailing input formats and output columns in a compact way. Every sentence adds value without redundancy.

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?

Despite no output schema, the description fully specifies the return CSV columns, and with 100% schema coverage for params, it leaves no critical gaps for correct usage. It adequately covers input formats, limits, and output structure.

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 schema already documents all parameters. The description adds meaningful context beyond the schema by detailing the exact CSV format expected (UniqueID,Street,City,State,ZIP) and precedence between csv_content and addresses, which aids correct invocation.

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 a specific verb (geocode) and resource (addresses, locations only) with a clear scope limit ('no Census geographies'). This distinguishes it from sibling batch_geocode_geographies and the oneline/parsed geocode tools by its batch + locations-only nature.

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 for bulk location geocoding and hints at format choices, but does not explicitly say when to use this vs single-address siblings (geocode_oneline_address, geocode_parsed_address) or when to prefer CSV over array input beyond precedence. No when-not guidance.

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