geolocate_ip

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

Discloses that omitting the IP returns the requester's own IP, and that data includes location, ISP, timezone. Could mention potential errors or data source, but acceptable for a simple lookup.

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?

Efficiently structured: purpose, usage paragraph, parameter details. Every sentence adds value without redundancy.

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?

Covers essential aspects: what the tool does, parameter details, default behavior, and typical use cases. Could mention error handling or support for IPv6, but sufficient for a simple tool.

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 description explains the ip_address parameter with an example and default behavior ('If empty or omitted, returns data for the requester's own IP'), adding meaning beyond the schema's title and type.

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 'Get geolocation data for an IP address' with specific verb and resource. Distinguishes from sibling tools like geocode (address to coordinates) and reverse_geocode (coordinates to address) by focusing on IP lookup.

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?

Provides clear usage context: fraud detection, analytics, geo-targeting, debugging. Does not specify when not to use it or mention alternatives, but the use cases are well-defined.

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