Reverse Geocode

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

No annotations provided; description only says 'nearest known address' without detailing coverage, accuracy, or failure behavior. Missing info on search radius default and what happens if no address found.

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?

Two clear sentences with no waste. Front-loaded with core purpose, then optional parameter hint.

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?

Tool has 4 params and no output schema. Description does not explain return format or edge cases (e.g., no result). Lacks completeness despite good schema 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 covers 100% of parameters. Description adds 'Restrict to a specific country', repeating schema info. No new semantic value beyond schema.

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?

Clearly states verb 'convert' and resource 'latitude / longitude pair into address'. Distinct from siblings: geocode (forward), postcode_lookup, validate_address. Explicitly mentions country restriction.

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?

Implies usage for reverse geocoding but does not explicitly state when to use alternatives (e.g., geocode for forward). Lacks when-not-to-use guidance.

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