ensure_real_tab

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

The description discloses the behavioral trait of auto-navigating to about:blank when the current tab is an internal chrome:// page, and states the return format. Since no annotations are provided, the description carries the safety/disclosure burden. It partially addresses this but doesn't mention side effects (e.g., whether it navigates existing tabs, whether it affects user session/history, or what happens if the tab is already a real page).

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 two concise sentences covering purpose, trigger condition, and output. It's compact but covers the key information. Slightly terse but no wasted words.

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?

The tool is simple (0 params, no output schema), so the description covers the core function. However, it doesn't clarify edge cases like what constitutes an 'internal page', whether the navigation is synchronous, or what the {url, title} represent post-navigation. Adequate for a simple utility but could note more behavioral details.

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?

With 0 parameters, the description has no parameter semantics to explain. The baseline for 0 params is 4, and the description appropriately explains the tool's behavior and output format despite having no inputs.

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 verb ('ensure'), the resource ('tab'), and the specific behavior (auto-navigate to about:blank when the current tab is an internal chrome:// page). It returns {url, title}. This is specific and distinguishes it from siblings like navigate or new_tab.

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 the use case: for navigating from internal pages to a real page before performing actions. However, it doesn't explicitly state when to use this vs alternatives (e.g., navigate to about:blank directly, or new_tab). Usage context is clear but not contrasted with sibling tools.

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