ghost_tab_close

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the action without noting that closing is irreversible, what happens to unsaved state, or whether confirmation is needed. The tool name and verb imply destruction, but the description does not make behavioral consequences explicit.

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 front-loaded sentence with no filler. It immediately conveys the operation and target. While terse, every word earns its place.

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 tool with no output schema, no annotations, and zero schema description coverage, this description is too thin. It fails to explain the optional browser parameter, any side effects, or how this interacts with the tab lifecycle. An agent would likely need to infer or probe behavior to use it confidently.

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 both parameters. It clarifies that the tab is referenced 'by id,' which maps to the required 'tab' parameter, but it does not mention the optional 'browser' parameter at all. This leaves the agent without semantic guidance for half of the input schema.

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 states a specific verb and resource: 'Close a tab by id.' This clearly distinguishes it from sibling operations like ghost_tab_open, ghost_tab_navigate, and ghost_tab_click. The scope is unambiguous for an agent selecting among many tab-related tools.

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 provides no guidance on when to use this tool versus alternatives, such as ghost_browser_close for closing an entire browser or ghost_reset for broader cleanup. There are no stated exclusions, prerequisites, or context cues. An agent must infer usage entirely from the tool name and sibling set.

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