proxy_rotate

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

Description discloses that the tool forces rotation and returns the new IP, which is sufficient behavioral context. However, it does not mention any side effects like invalidating existing sessions or rate limits. Since no annotations are provided, the description carries full burden, but it adequately covers the core behavior.

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, zero waste: states what it does and what it returns. Optimal for the tool's simplicity.

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 low complexity (1 optional param, no output schema, no nested objects), the description is sufficiently complete. It covers purpose, action, and outcome. Minor gap is lack of explicit statement about any prerequisites.

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?

Only one optional parameter with 100% schema coverage; description does not add meaning beyond schema's '2-letter country code (optional).' Baseline 3 is appropriate as schema already explains the parameter.

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's action ('force IP rotation'), method ('fetching with a new random session'), and outcome ('returns the new exit IP to confirm rotation'). It is distinct from siblings like proxy_check_ip which checks current IP, and proxy_fetch which likely fetches a page.

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?

Description implies when to use (when a new IP is needed) and provides confirmation mechanism. It does not explicitly state when not to use or mention alternatives, but the purpose is self-evident given sibling names.

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