proxy_check_ip

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

No annotations provided, so description carries burden. It mentions 'auto-rotate if omitted' which is a key behavioral trait. However, it does not disclose whether the tool is read-only, potential side effects (e.g., token consumption), or error states.

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 purpose, concise and to the point. No unnecessary words.

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?

Tool is simple (1 optional param, no output schema). Description covers purpose and key behavior (auto-rotation). Could mention return format (IP, geo) but not critical for a simple check 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?

Schema coverage is 100% (country param described). Description adds context that country is optional and auto-rotation occurs if omitted, which goes beyond schema. However, no other parameters exist, so baseline 3 is appropriate.

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?

Description clearly states the tool checks 'exit IP address and geo-location' and its purpose to 'verify which country/region' the proxy is using. Distinct from siblings like proxy_fetch or proxy_rotate.

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 when to use: to verify proxy location. Does not explicitly mention when not to use or alternatives, but the context is clear enough. Siblings like proxy_list_countries or proxy_rotate imply alternatives for different needs.

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