geocode_address

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

The description adds significant behavioral context beyond annotations: it discloses return payload details (coordinates, formatted address, address components, confidence score, provider name), the 'up to limit' behavior, and the fact that the country parameter biases rather than strictly filters results. This goes well beyond the readOnly and idempotent hints.

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 two sentences long, front-loaded with the core purpose, and every clause adds relevant information. No filler or redundancy exists.

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 having no output schema, the description sufficiently explains return values and key behaviors. It covers candidate results, output fields, and the country bias. Minor gaps include error handling or edge cases (e.g., no match), but these are not critical for a simple geocoding tool with good annotation coverage.

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 fully documents all three parameters. The description only restates the country parameter's bias behavior already present in the schema, adding no additional semantic meaning beyond what the input schema provides.

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 uses a specific verb ('Convert') and resource ('street address or place name into geographic coordinates'), making the tool's function immediately clear. It distinguishes itself from siblings like reverse_geocode (coordinates to address) and zip code tools by focusing on address-to-coordinate conversion.

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: when you have an address or place name and need coordinates, use this tool. However, it does not explicitly mention alternatives or exclusions, such as 'for reverse geocoding, use reverse_geocode instead,' leaving some ambiguity relative to its sibling tools.

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