Get My IP Address

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

Beyond the readOnlyHint annotation, the description adds that it returns a plain IP string (not geolocation) and requires no authentication or credits. This fully discloses behavior and limitations.

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 that efficiently convey purpose, usage boundaries, and return type. No redundancy or irrelevant details. Information is 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?

Despite lacking an output schema, the description clearly states the return value (plain IP string) and distinguishes it from more complex sibling tools. Covers all needed aspects for this simple, zero-parameter 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 tool has no parameters, and the description correctly confirms 'Takes no input parameters'. With 0 parameters and 100% schema coverage, no additional parameter detail is needed (baseline 4).

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 states 'Return the public IP address of the machine running this MCP server' with a specific verb and resource. It distinguishes itself from the sibling tool lookup_ip by noting it does not provide geolocation data.

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?

Explicitly states when to use: 'only when the user asks for the server or caller public IP' and when not: 'use lookup_ip for location, ASN, timezone, currency, security, or abuse data'. Also notes no API key or credits required.

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