pilot_tabs

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

With no annotations provided, the description must fully disclose behavior. It states the tool returns a list and that no errors occur, but does not explicitly confirm it is read-only or describe any side effects. The non-destructive nature is implied but not stated.

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 at three short sentences, each adding value: purpose, usage, return format, and error handling. It is front-loaded with the core action and information.

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 description covers purpose, usage, and return format, but lacks output schema to confirm the structure. It does not specify if tabs are from the current window or all windows, which could be ambiguous. Slight gap for a simple listing tool.

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 tool has zero parameters, and the description explicitly notes 'Parameters: (none)'. Since schema coverage is 100% and no parameters exist, the description adds clarity that no input is required.

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 lists all open browser tabs with their IDs, URLs, titles, and active status. It distinguishes itself from sibling tab tools (e.g., pilot_tab_close, pilot_tab_new) by focusing on listing rather than manipulation.

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 says when to use the tool: to see what tabs are open, find a specific tab, or check the active tab. It does not explicitly state when not to use it, but the context of listing makes it clear this is for observation, not for tab management.

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