maps_geocode

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

With no annotations provided, the description carries the burden of behavioral disclosure. It clearly conveys a read-only conversion operation and the core input-output behavior, but it does not disclose edge-case behavior, coordinate format details, or limitations. For a simple stateless geocoding call, this is adequate but not rich.

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 concise sentence with no filler. The verb and key transformation are front-loaded, making it easy for an agent to parse quickly.

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 a single-parameter geocoding tool, the description is sufficient for selection and invocation: it defines the input and states the output as coordinates. It does not describe the exact output schema, but none is present, and the 'latitude/longitude' phrasing gives enough context. The only real gap is the lack of explicit guidance for choosing between this and sibling tools.

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 100%, and the 'address' parameter is already documented in the schema. The description adds helpful context by clarifying that the address can be a street address or place name, but the schema already carries the main semantic weight, so baseline 3 is appropriate.

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 names the resource ('street address or place name') and the output ('latitude/longitude'), so an agent can tell what the tool does. It does not explicitly contrast with siblings like maps_search_places, which could also return location data, so sibling differentiation is only implicit.

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 when to use the tool: when you have an address or place name and need coordinates. However, it does not explicitly state when not to use it or name alternatives, leaving some routing inference to the agent.

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