firefox_tab_action

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description earns no credit merely for implying closing is a write. It does add one useful piece of context beyond annotations: the unsaved-work warning on close. It says nothing about what happens after close (focus shift, whether tabId becomes invalid), nor about rate limits or failures.

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?

Two short sentences with the operation list front-loaded and the hazard sentence last, which is the right order. No padding, though 'authorized' is a slightly murky qualifier.

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?

This is a mutation tool with no output schema and two undocumented parameters, so the description should do more than restate the enum. It covers the safety caveat for close but leaves the tabId source and the post-action effects (especially for close and activate) unexplained.

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%, so the description must carry parameter meaning and does not. The action list merely restates the enum, and tabId gets no explanation at all — no hint that it comes from firefox_list_tabs or what a valid tabId means.

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 specific resource (an authorized tab) and enumerates the concrete operations: activate, reload, pin, unpin, close. That distinguishes it from siblings like firefox_open_tab and firefox_release_tab, though the word 'authorized' is never explained and the boundary with firefox_release_tab is left implicit.

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?

Use is implied by the action list: pick this when you already have a tabId and need a lifecycle operation. There is no explicit when-to-use vs. an alternative, and no guidance on how it relates to firefox_open_tab (new tab) or firefox_release_tab, which an agent could reasonably confuse with pin/unpin.

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