scout_open

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

Discloses important behaviors: clears old tabs, resets API pool, does not navigate, and returns status. However, with no annotations, it lacks details on authentication, rate limits, or potential side effects beyond clearing tabs.

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?

Very concise and well-structured: purpose first, then specific actions, then a critical contrast (not for navigation), and finally return value. No wasted sentences.

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?

Given no annotations and an output schema (not shown), the description covers the tool's core functionality and return value. It could be slightly more explicit about being the first step in a sequence, but is otherwise 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?

Tool has zero parameters and schema coverage is 100%, so the description does not need to add parameter info. Baseline score of 4 is appropriate as the description adds context without needing to explain params.

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 the tool opens/manages a browser session, with specific actions like finding/launching Chromium and clearing tabs. It explicitly distinguishes itself from scout_goto for navigation.

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 a positive use case (opening/managing session) and a clear exclusion (not for navigation, use scout_goto). However, it does not explicitly discuss when to avoid using it relative to other sibling tools like scout_close or scout_tabs.

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