get_tabs

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

With no annotations provided, the description carries full burden. It describes the return format (list of tabs with index, name, current) and implies no side effects. It could explicitly state idempotency or session validity, but is sufficient for a read operation.

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 well-structured with Purpose, Parameters, and Returns sections. It is concise, uses minimal words, and front-loads the main action. Every sentence adds value.

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 read tool with one parameter, the description covers the main purpose and return schema. However, it omits error handling (invalid session, empty tabs) and does not explain all fields in the return dict (e.g., status, message). Slightly incomplete.

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?

Input schema has 0% coverage, but the description adds meaning: 'Active browser session identifier.' This compensates for the lack of schema description, providing necessary context for the single parameter.

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 'Retrieve all open browser tabs for the current session,' using a specific verb and resource. It distinguishes from siblings like get_current_tab (single tab) and switch_tab (action) by clarifying it returns all 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?

The description says 'so the agent can decide which tab to switch to,' implying usage context. However, it does not explicitly mention alternatives or when not to use, missing the chance to differentiate from get_current_tab.

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