Network/Routing Info

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

Annotations already set readOnlyHint=true, and the description adds cost (1 credit), cache bypass behavior for force_refresh, and return structure. No contradictions. Could mention rate limits but not essential for this tool.

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-sentence first paragraph gives overview, second paragraph covers parameters and usage. No redundant information, front-loaded with key action and resource. Highly efficient.

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 tool with 2 optional parameters and no output schema, the description covers purpose, usage, cost, param details, return structure, and differentiation from siblings. Nothing essential 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?

Schema coverage is 100%, baseline 3. The description adds value by explaining that omitted ip means caller IP (beyond schema's 'omit to check caller's IP'), and that force_refresh bypasses cache and can consume credits, which is not in 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 states 'Read-only network lookup via GET /v3/ipgeo' and specifies the returned fields (route CIDR prefix, connection_type, is_anycast). It explicitly distinguishes from sibling lookup_ip by advising to use this tool for network-only requests and lookup_ip when additional data is needed.

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?

Provides explicit guidance: use for network-only requests, avoid when needing location/ASN/etc. (suggesting lookup_ip), explains ip omission behavior, force_refresh usage condition ('only when the user asks'), and mentions cost (1 credit) implying judicious use.

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