Rotate identity

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

With no annotations, the description carries the full burden. It discloses two key behaviors: rotating to a new IP (same country) and clearing cookies. This is transparent for a rotation tool, though it could mention if it preserves any session data beyond cookies.

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 consists of two well-structured sentences: the first explains the action, the second gives usage guidance. No extraneous information; every word earns its place.

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 simple tool with one parameter and no output schema, the description covers purpose, behavior, and usage. However, the lack of parameter documentation is a clear gap, making it merely adequate rather than fully complete.

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 schema has one required parameter (session_id) with no description. The tool description mentions 'session' but does not explain what session_id is, how to obtain it, or any format constraints. Given 0% schema coverage, the description should compensate but does not.

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 rotates the session to a fresh residential exit (new IP, same country) and clears cookies. The verb 'rotate' and resource 'session' are specific, and the outcome (new IP, same country) distinguishes it from sibling tools like aethyn_check_exit_ip, which only checks the current IP.

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?

The description explicitly says to use it 'between independent tasks or after a soft-block,' providing clear contextual guidance. However, it does not mention when not to use it or offer alternatives (e.g., just checking IP), which would make it a 5.

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