Change proxy country / operator

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

Discloses that the proxy login/password remains unchanged, that it's a physical location swap, and that a per-proxy cooldown applies. Annotations (readOnlyHint=false, destructiveHint=false) are non-contradictory; description adds behavioral detail beyond them.

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?

Three sentences, front-loaded with purpose, then parameter guidance, then optional verification and cooldown. Every sentence adds necessary information.

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?

Covers usage, parameters, behavior, and constraints (cooldown). No output schema but operation is clear. Could mention error handling or cooldown expiration check, but still sufficient given schema coverage and annotations.

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%, so baseline is 3. Description adds value by explaining the relationship between parameters (e.g., geoid is most specific, pass at least one) and the effect of check_after_change.

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 swaps the underlying modem of a proxy to a different country/operator without buying a new proxy, distinguishing it from siblings like rotate_ip and buy_proxy.

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?

Describes required parameters (at least one of country, id_country, geoid, operator) and optional check_after_change. Mentions cooldown. Could be improved with explicit when-not to use compared to rotate_ip or buy_proxy.

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