ip_geolocate

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

Description mentions approximate location and accuracy radius but lacks critical behavioral details such as rate limits, authentication requirements, or error handling for invalid IPs. With no annotations, the description should provide more transparency.

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 concise sentences front-load the core purpose and add a key detail about reverse geocoding with no wasted 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?

While parameter descriptions are complete, the description omits output structure and error scenarios. Given no output schema, a brief mention of return fields would improve completeness.

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 all three parameters with descriptions, and the tool's description adds context for 'reverse_geocode' and 'language' by linking them to the optional reverse geocoding feature, enhancing understanding 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?

Description clearly states the tool estimates geographic location from an IP address via Google's Geolocation API, distinguishing it from sibling tools like geolocation_estimate which may use other methods.

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?

No explicit guidance on when to use this tool versus alternatives like geocode_reverse or geolocation_estimate. Agent must infer usage from context alone.

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