scout_new_tab

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

With no annotations, the description must cover behavioral traits. It mentions optionality of the URL but does not disclose side effects (e.g., whether focus shifts to new tab, whether it waits for page load, or if any errors are returned). The description provides basic transparency but lacks depth.

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?

The description is a single, clear sentence with no extraneous words. It efficiently communicates the tool's purpose and optional behavior.

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 the tool's simplicity (1 optional param, no output schema), the description is minimal but incomplete. It does not explain what happens when no URL is provided (e.g., opens a blank tab or default page), nor does it describe any return value or confirmation. This could lead to uncertainty for the agent.

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?

The schema covers 100% of parameters with a description for 'url'. The description adds the key nuance that navigation is optional, which is not explicit in the schema. This clarifies the parameter's optional nature and typical usage.

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 the action ('Open a new browser tab') and the resource (new tab), with optional navigation. It effectively distinguishes from sibling tools like scout_navigate (which navigates current tab) and scout_switch_tab (which switches to existing tabs).

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?

No guidance is provided on when to use this tool over alternatives like scout_navigate or scout_switch_tab. The description lacks context about appropriate scenarios or prerequisites, which is particularly important given the number of related sibling tools.

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