pilot_tab_new

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

Without annotations, the description discloses return values (tab ID and URL) and error conditions (invalid URL). It does not detail if the tab is focused or other behaviors, but covers key aspects.

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 concise with a clear main action. It then lists parameter, returns, and errors, which is structured but slightly verbose given the simple tool.

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 simple tool with no output schema or annotations, the description covers purpose, parameter, returns, and errors. It is complete enough for an agent to use correctly, though behavioral details like tab focus are missing.

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 the parameter 100%, and the description adds meaningful context: 'url is optional, omit for blank about:blank tab'. This clarifies usage beyond the schema's description.

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 tool opens a new browser tab with an optional URL. It distinguishes from siblings like pilot_tab_select and pilot_tab_close by focusing on creation.

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 explicitly lists use cases: opening a link in a new tab, creating a blank tab, or working with multiple pages. It provides clear context but does not mention when not to use or alternative tools.

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