ghost_tab_screenshot

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

With no annotations provided, the description carries the full behavioral burden. It usefully discloses that the screenshot is rendered by the tab itself and does not require the tab to be in front or focused, addressing the most likely behavioral surprise. It also specifies PNG output, though it does not discuss side effects or whether the tab must already be loaded.

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 a single efficient sentence that front-loads the core purpose ('PNG of a tab') and then adds the distinguishing behavioral caveat. Every word contributes meaning; there is no filler or repetition.

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 relatively simple, but the complete absence of parameter descriptions, combined with no output schema and no annotations, leaves notable gaps. The description adequately conveys the main operation but does not fully equip an agent to correctly set optional parameters or handle the return value beyond knowing it is a PNG.

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 compensate for the undocumented parameters. It clarifies that 'tab' is the target of the screenshot, but it gives no meaning for 'browser' or 'full_page', leaving an agent to guess whether full_page captures the entire scrollable page and whether browser selects a specific browser instance.

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 produces a PNG of a specific tab, and the key qualifier 'regardless of whether it is in front or focused' distinguishes it from general screenshot tools like ghost_screenshot. It identifies the resource (tab), the output format (PNG), and a defining behavioral characteristic in a single focused sentence.

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 implies when to use this tool: when you need a tab's visual rendering even if it is not foreground or focused. However, it does not explicitly name alternatives such as ghost_screenshot or ghost_snapshot, nor does it state when those should be preferred instead.

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