ip_lookup

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds nothing beyond them — no mention of the upstream provider, rate limits, whether api_key is needed for higher quotas, or which fields come back (country/city/coords/ISP), all of which matter for an external network call.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, but the terseness is arguably under-specification rather than true concision given the undocumented second parameter.

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?

No output schema exists, so the description should indicate what a geolocation result contains; it does not. Combined with 0% parameter coverage and no disambiguation from sibling IP tools, an agent has too little to call this correctly beyond the happy path.

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 description coverage is 0%, so the description carries the full burden and does not meet it. It never mentions api_key at all — the agent cannot tell whether that parameter is optional, how to obtain it, or what happens if it is omitted or invalid.

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?

Names a specific verb ('look up') and resource ('geolocation for an IP address'), so the core operation is unambiguous. However, it makes no attempt to distinguish itself from the many near-identical siblings (ipinfo_lookup, ip_address_lookup, country_by_ip, ip_batch), leaving the agent to guess which IP-geo tool to pick.

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?

There is no when-to-use guidance at all: no mention of how this differs from ipinfo_lookup or ip_address_lookup, no note on batch vs single lookups, and no prerequisites or exclusions. With this many overlapping siblings, the absence of routing guidance is a real gap.

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