navigate

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

No annotations are present, so the description carries the transparency burden. It states it returns visible text, which is helpful. However, it doesn't disclose loading/wait behavior, whether navigation occurs in a fresh page or the same tab, or what happens on failed/404 navigation. The require_auth parameter hints at auth implications but its behavioral effect isn't described.

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?

A single, focused sentence that states what it does and what it returns. Efficient and front-loaded. Could arguably add a note on auth but remains appropriately concise.

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 general navigation tool with no output schema and no annotations, the description is moderately complete. It covers purpose and return value but omits behavioral details like auth requirements (the require_auth param is unexplained), page load waits, and error behavior. Given the tool's broad scope, more detail on auth and failure modes would improve completeness.

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 both parameters are documented in the schema itself. The description adds no new param-level semantics beyond the schema. Baseline 3 is appropriate since the schema already does the heavy lifting.

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?

Clear verb+resource+scope: 'Navigate the automation browser to any LinkedIn path or absolute URL and return visible text.' It distinguishes from siblings by covering browser navigation broadly, while other tools handle specific LinkedIn resources.

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 implies it's a general-purpose navigation tool ('any LinkedIn path or absolute URL'), but provides no explicit when/why to use it vs. other tools. Given the many specialized tools (search_jobs, get_profile, etc.), it would help to state when raw navigation is appropriate, e.g., for pages without a dedicated tool.

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