geocode.address

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

No annotations are provided, so the description carries full burden. It mentions the data source (LocationIQ, OSM/ODbL) but fails to disclose important behavioral traits like world-wide coverage, attribution requirements, rate limits, or output format. This is insufficient for an unannotated tool.

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 efficient sentence that front-loades the core purpose. It contains no wasted words. However, it could be restructured to include more critical details without adding bulk.

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 simple tool with no output schema and minimal annotations, the description should provide more context about the return format, error handling, or usage restrictions. It lacks completeness for an agent to reliably invoke and interpret results.

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 schema already describes two of three parameters (q and country) with 'description' fields. The description adds no extra meaning beyond the schema. Schema coverage is 67%, so baseline is 3. The parameter descriptions in the schema are adequate for basic understanding.

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 clearly states the tool performs forward geocoding from a free-text address to a coordinate, and distinguishes from the sibling geocode.reverse tool. The mention of the underlying service (LocationIQ, OSM/ODbL) adds specificity.

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 for forward geocoding but does not provide explicit when-to-use or when-not-to-use guidance. It does not mention alternatives or exclusions, though the sibling list includes geocode.reverse for reverse geocoding.

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