browser_tab_current

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

No annotations are provided, so the description carries the full behavioral burden. 'Get' weakly implies a read-only, non-mutating call, but the description says nothing about whether a session must be attached to a live browser, what happens if no tab is active, or whether the read is side-effect free. An output schema exists, so return format need not be restated, but the remaining gap is large for a tool with zero annotation coverage.

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?

A single short sentence with no filler and no burying of the key concept. It is efficient, though the terseness is partly under-specification rather than disciplined editing.

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 and has an output schema covering return values, so the description need not explain results. But with no annotations, an undocumented required parameter, and no routing guidance among many tab-related siblings, an agent is left guessing about preconditions and scope.

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?

Schema description coverage is 0% for the single required parameter session_id, so the schema contributes nothing. The description does not mention session_id at all — it neither states that it identifies the browser session nor what form it takes — leaving the parameter undocumented in both structured and unstructured data.

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 names a verb ('Get') and a resource ('active tab summary'), so the basic action is inferable. However, 'summary' is undefined — it is unclear whether it returns a title/URL pair, DOM state, or something else — and nothing distinguishes it from the sibling browser_tab_list or browser_snapshot. Purpose is recognizable but vague on scope.

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?

There is no statement of when to use this tool versus alternatives such as browser_tab_list (all tabs) or browser_snapshot (page content), nor any precondition or context requirement. The only implied usage is 'you want the current tab', which the name already conveys.

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