Geocode address

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It describes the output structure (list of matches with coordinates, formatted address, admin boundaries, OSM type/ID, bounding box, importance ranking) which is helpful, but it does not mention potential edge cases such as ambiguous addresses, multiple matches, or failure behavior. The description gives a reasonable but not exhaustive view of the tool's behavior.

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, well-structured sentence that front-loads the core action and quickly enumerates the key output fields. Every clause adds meaningful information without redundancy or rambling.

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?

This is a simple tool with one parameter and no output schema. The description sufficiently explains the tool's purpose and return values, making it complete for most use cases. A minor gap is that it doesn't mention how multiple matches are ranked or potential limitations, but given the tool's simplicity, this is not a critical omission.

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?

The input schema has 100% coverage with a detailed description for the 'address' parameter, so the baseline is 3. The tool description adds minimal additional semantic value beyond the schema, though it does confirm that the address can be a place name or landmark. The schema already provides examples, so the description does not need to compensate.

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 clearly identifies the resource (an address or place name) and the outcome (geographic coordinates). It also enumerates the detailed location information returned, effectively distinguishing this from sibling tools like reverse_geocode which performs the opposite operation.

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 the primary use case (geocoding an address) but does not explicitly state when to use this tool versus alternatives. There is no mention of when not to use it or which sibling tool would be more appropriate for reverse geocoding or place discovery. However, the context is clear enough for a competent agent to infer the tool's role.

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