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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: the 5-address batch cap, the cleaned/matched address with match confidence, and the differing backends (US Census geocoder vs OpenStreetMap) for US and worldwide addresses.

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?

Three tight sentences: core conversion first, then US-only enrichments, then the worldwide fallback. Nothing is padding and every clause carries new information.

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?

With no output schema, the description does the heavy lifting by naming the returned fields (coordinates, cleaned matched address, match confidence, FIPS codes). It omits failure behavior for unmatched or mixed US/non-US batches and any rate/accuracy caveats, which keeps it short of a 5.

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 baseline is 3. The description adds value beyond the schema by spelling out exactly what include_districts returns (congressional, state legislative, city, school district, metro area) and tying country values to the US-Census-versus-OSM backend split.

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 precise verb and resource ('Convert ... street addresses to latitude/longitude') and enumerates the derived outputs. The forward direction inherently distinguishes it from the sibling reverse_geocode, so an agent can route correctly without opening the schema.

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 explains what US versus worldwide lookups return and what include_districts unlocks, which implies usage, but never states when to pick this over reverse_geocode or what happens with ambiguous/unmatched addresses. Usage is inferable rather than stated.

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