network_my_ip

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

Without annotations, the description must disclose behavior. It states it finds public IP and details, which implies a read operation. However, it doesn't mention how the tool obtains the data, any network requirements, or privacy implications. The mention of 'full page guidance' suggests more info exists but isn't included.

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 relatively short but contains redundancies like 'Menu ID: my_ip' and 'My IP Address' which could be omitted. The core information is in two sentences, but the tooltip-like structure could be more streamlined.

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?

Given no output schema, the description should explain what the tool returns. It mentions seeing external IP, ISP, location, and network information, which is sufficient for a simple lookup. However, it lacks details on the format or structure of the output. The pointer to describe_tool fills some gaps but leaves the description incomplete on its own.

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 required parameters, and the schema accepts additional properties. The description implies no input is needed ('See your external IP'), which aligns with zero parameters. For a tool with no parameters, the description adequately conveys that no arguments are required.

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 the tool finds the user's public IP address and associated information (ISP, location, network). It emphasizes 'your public IP' distinguishing it from siblings like network_ip_geolocation which look up arbitrary IPs.

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 on when to use this tool versus alternatives like network_ip_geolocation or network_asn_lookup. The only hint is 'Use describe_tool', which is circular. A tool with overlapping functionality should clarify its specific use case.

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