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

Annotations already mark the operation as read-only and non-destructive. The description adds that a free key is required and that the lookup returns privacy/hosting flags, backed by a concrete example, making the external credentialed nature of the tool clear. It does not cover rate limits or failure modes, but the annotation coverage lowers the bar here.

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: capability summary, key prerequisite, and concrete example. Every sentence adds distinct information, and the most important scoping details are front-loaded.

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 one-parameter, read-only lookup with no output schema, the description provides the data categories, the authentication requirement, and an example of expected output. Nothing necessary for an agent to call the tool correctly is missing.

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 single required parameter 'ip' is already fully described in the schema with type and length constraints, and schema coverage is 100%. The description reinforces this with an example value and its effect on output, but does not need to add much parameter-level meaning beyond the 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?

The description clearly characterizes the tool as a comprehensive single-IP intelligence lookup, enumerating geolocation, network/ASN, privacy, hosting, and threat categories, and the example shows expected output. It does not explicitly name or contrast sibling tools such as ip_lookup_lite or ip_lookup_batch, so differentiation is only implied by 'MAX' and 'Full'.

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?

Usage context is implied: 'Full IP intelligence' plus the MAX/LITE sibling names suggests choosing this for comprehensive single-IP data, and the free-key requirement is stated. However, there is no explicit when-to-use vs when-not-to-use guidance, and alternative tools are not named.

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