Verify exit IP / geo

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

No annotations provided, so description carries full burden. Describes read-only behavior ('Fetch IP info') and lists return fields (ip, country, city, etc.). Does not explicitly state lack of side effects, but the verb 'fetch' strongly implies read-only. Sufficiently transparent for a simple query.

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?

Single sentence, front-loaded with action and purpose, efficiently enumerates return fields. No wasted 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?

Covers action, purpose, and return values explicitly. For a one-parameter read-only tool without output schema, this is sufficient. Could mention prerequisite of an active session, but parameter name implies that.

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 has 0% parameter description coverage; the single required parameter 'session_id' is not described in the tool description. Parameter name is self-explanatory, but the description fails to add semantic context or guidance on how to obtain it, relying solely on agent inference.

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 action: 'Fetch IP info THROUGH the session's proxy' with specific verb and resource. Distinguishes from sibling tools like aethyn_navigate or aethyn_launch_browser by focusing on verification of proxy exit location.

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 implied usage context ('verify the exit country/city actually landed before trusting the page') but lacks explicit when-not-to-use or alternative tool references. No mention of alternatives among siblings.

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