IPStack MCP Adapter

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

Annotations already establish readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact, the plan-tier prerequisite, but says nothing about per-request IP limits, partial-failure behavior, or rate limits for a bulk endpoint.

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 sentences, front-loaded with the return payload then the use cases and prerequisite. The long parenthetical field list is dense but earns its place given there is no output schema, though it could be trimmed.

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?

With no output schema, the description's enumeration of returned fields (country, region, ISP, proxy/tor/threat flags, etc.) is the only place an agent learns the response shape, and the plan prerequisite is captured. Missing are bulk-specific details such as how many IPs are allowed per call and how failures for individual addresses are reported.

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 100%, so all five parameters (including the unusual model and include_optional flags) are already documented in the schema. The description adds no parameter-level syntax or semantics beyond what the schema provides, which is the baseline-3 case.

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?

States a specific verb ('Get') and resource ('geolocation and security details') and explicitly scopes it to 'multiple IPv4 or IPv6 addresses in one request', which separates it in spirit from the singular ipstack_lookup sibling. It never names the siblings, so an agent must infer the bulk-vs-single distinction rather than being told it.

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?

Gives concrete use cases ('analyzing lists of IPs, grouping by country/region, or flagging suspicious origins') and a real prerequisite ('Requires a plan that supports bulk lookups'). It stops short of naming ipstack_lookup as the alternative for single-address queries or stating any when-not condition.

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

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

Annotations already declare readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful semantics beyond that: the resolved address belongs to the calling client/platform and is 'not necessarily the end user's own device or network' — a caveat that changes how an agent should interpret the result. It stops short of mentioning rate limits, auth, or result caching.

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?

Three sentences, front-loaded with what is returned and then the routing caveat. The long parenthetical field list is a bit dense but earns its place by previewing output in the absence of an output schema.

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?

With no output schema, the description compensates by enumerating the returned fields, and it clarifies the origin-IP semantics. The one gap is that it never acknowledges the optional include/verbose/include_optional controls, which are the only knobs an agent could set.

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 coverage is 100%, so the schema already documents model, include, verbose, and include_optional well. However, the description asserts 'Takes no parameters,' which is factually at odds with the four optional parameters in the schema and could lead an agent to skip include/verbose. The misleading claim pulls this below the 3 baseline.

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?

Opens with a specific verb+resource ('Return geolocation and security details ... for the IP address this request appears to originate from') and even enumerates the returned field categories. It explicitly distinguishes itself from the sibling ipstack_lookup, so an agent can route correctly without opening either schema.

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?

States exactly when to use this tool (origin IP of the current MCP call) and names the alternative for the other case ('To look up a specific IP address, use ipstack_lookup'). Selection criteria are explicit, not inferred.

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

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

Annotations already establish readOnlyHint=true, openWorldHint=true, destructiveHint=false, so the safety profile is covered. The description adds that responses include proxy/tor/threat flags, which is useful content context, but says nothing about rate limits, auth, or error behavior.

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 sentence, front-loaded with the verb and resource, with the field list parenthetical doing real work. The long enumeration makes it slightly dense but nothing is wasted.

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?

With no output schema, the description carries the return-value burden and largely does so by listing fields. Minor gap: it lists fields such as proxy_type and threat_types that actually require the include/include_optional parameters, implying a default set that the schema contradicts.

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 100% across all five parameters, so the schema already documents ip, model, include, verbose, and include_optional thoroughly. The description adds no syntax, format, or default-behavior detail beyond what the schema supplies, so baseline 3 applies.

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?

States a specific verb (Get) and resource (geolocation and security details) and enumerates the returned fields, so the agent knows exactly what comes back. The phrase 'for a single IP address' distinguishes it from the sibling ipstack_bulk_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?

The 'single IP address' scope implicitly routes the agent away from ipstack_bulk_lookup, but no alternative or condition is named explicitly, and ipstack_check is never addressed. Usage is inferable rather than stated.

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