Navigate

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

With no annotations, the description discloses key behaviors: waits for load, returns HTTP status, final URL, and page title. It also mentions respecting site policies. Missing details on error handling or timeout 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 only: first states action and return values, second adds constraints and usage tip. No wordiness, front-loaded with key info.

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 return values and constraints but lacks details on error cases (e.g., invalid URL, timeout) or authentication. Output schema absent, but description compensates partially. Sibling names provide context for session_id.

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 0%, but the description partially explains the 'url' parameter via 'Navigate... to a URL'. However, 'session_id' is not explained, relying on context from sibling tools. Adequate but not fully compensating for lack of schema descriptions.

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 it navigates the browser to a URL and waits for load, specifying a distinct action. It also implicitly differentiates from siblings like aethyn_get_content by suggesting reading the page separately.

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 clear constraints: public data only, respect robots.txt, rate limits, and terms. Also hints at using aethyn_get_content to evaluate the response, but lacks explicit when-not-to-use or alternatives.

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