Geocode Addresses

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

The annotations already state that this is a non-read-only, non-destructive, idempotent operation with no open-world access. The description adds meaningful context beyond that: it requires a controlled local locator, rejects remote billing locators, and expects typed field mapping. It does not detail output creation or overwrite behavior, but the added constraints are substantial.

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 a single, front-loaded sentence with two tightly packed clauses separated by a semicolon. It wastes no words and immediately states the action, scope, and key constraint. The structure is efficient and easy to parse.

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 an eight-parameter tool with no schema descriptions, the description is too terse. It omits input table requirements, output feature class behavior, and optional filtering parameters like categories, country_codes, location_type, and output_fields. The output schema and annotations help, but the description leaves important operational details unaddressed.

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 description coverage is 0%, so the description must compensate for eight parameters. It only touches two: locator_path (controlled local locator, not remote billing) and address_fields (typed field mapping). The remaining six parameters, including in_table, out_feature_class, categories, country_codes, location_type, and output_fields, receive no semantic explanation anywhere.

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 names a specific verb and resource: batch geocoding an address table with a controlled local locator. It adds scope qualifiers (typed field mapping, rejection of remote billing locators) that help distinguish it from reverse geocoding or generic locator tools. However, it does not explicitly name a sibling alternative, so it falls short of a 5.

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?

It gives a clear positive condition (use a controlled local locator) and an explicit negative condition (remote billing locators are rejected). It does not name alternative tools or describe when another geocoding sibling should be chosen instead. The locator prerequisite is useful guidance, but the absence of alternatives keeps it from a 5.

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