geocode

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

No annotations are provided, so the description carries the full behavioral burden. It never states that this is a read-only lookup, whether it hits a network/geocoding service, rate limits, or what happens on ambiguous or empty results — only that `country` reduces ambiguity.

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?

Short and front-loaded: the purpose appears first, followed by the disambiguation hint. The indented `country` fragment is slightly awkward formatting but wastes no words.

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?

An output schema exists, so return values needn't be explained, and the core purpose is covered. However, with no annotations and undocumented `limit`/`query` parameters, an agent still lacks enough to invoke it confidently in edge cases.

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. It explains `country` well (ISO 2-letter code for disambiguation) but says nothing about `limit` (default 5, max 10) or the format/expectations for `query`, leaving two of three parameters undocumented.

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 specific verb+resource: finding coordinates of a place by name, with concrete examples (village, summit, parking, lake). It's clear what the tool does, though it doesn't explicitly differentiate itself from nearby siblings like find_pois or find_hiking_routes.

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?

There is no explicit when-to-use guidance or named alternative. The usage context (resolving a place name to coordinates) is only implied by the description, and nothing tells the agent when to prefer this over find_pois or route_between.

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