Geoip

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about the returned data fields, including proxy/hosting flags, but does not disclose rate limits, data freshness, accuracy, or input constraints. There is no contradiction with the annotations.

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 front-loaded sentence that names the operation and then lists the key result categories. Every word adds value, with no filler or unnecessary repetition.

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 single-parameter read-only lookup with an output schema and safety annotations, the description covers the core purpose. It is slightly incomplete because it omits input format expectations and does not help route between IP-related siblings.

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 only defines 'ip' as a string with no description, and schema description coverage is 0%. The phrase 'IP geolocation' implies the parameter is the IP address to look up, but the description does not add format requirements, accepted address types, or validation details.

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 identifies the tool as IP geolocation and lists the output categories (country, region, city, ISP, ASN, proxy/hosting flags). It is easy to understand, though it lacks a direct verb and does not explicitly distinguish itself from IP-related siblings like whois_ip or bgp_ip.

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 guidance is given about when to use this tool versus alternatives such as whois_ip, bgp_ip, or shodan_internetdb. The field list implies a geolocation use case, but the description provides no explicit context, exclusions, or prerequisites.

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