navigate_session

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

Discloses return values (URL/title + screenshot) and hints at reload behavior for persistence. However, without annotations, it omits details on error handling, prerequisites (session must exist), and whether it waits for navigation to complete, which are important for reliable use.

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: first defines purpose, second adds specific guidance. No redundant information, front-loaded with key details.

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 purpose, return values, and one use case. Lacks details on return format structure (e.g., what 'screenshot' means), prerequisites, and failure modes. Adequate for simple tool but could be improved with more specifics.

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 covers both parameters with descriptions. The description adds value by noting that reload is for state persistence, providing extra context beyond the enum values.

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?

Clearly states it performs browser history navigation (back/forward/reload) and returns new URL/title + screenshot. No sibling tool duplicates this specific function, so it stands out.

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?

Explicitly mentions reload is useful for testing state persistence, giving a concrete use case. Lacks explicit guidance on when to avoid using it (e.g., instead of clicking a back button), but the context is clear enough for typical usage.

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