create_firefox_tab_group

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

With no annotations, the description carries the full burden. It discloses post-creation verification and the duplicate-title failure condition, but omits the behavior around pinned tabs (allowUnpin), any permission requirements, or what happens if the input contract is violated. Partial transparency.

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, information-dense sentence that front-loads the main action and includes the key caveats. No wasted words.

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 has 4 parameters, no output schema, and no annotations. The description covers the core operation and a failure mode, but doesn't mention return value, pinned-tab behavior without allowUnpin, or prerequisites like the Firefox bridge. Schema descriptions help fill some gaps but not all.

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 100%, so the baseline is 3. The description adds a bit of context (exact title matching, same-window constraint) but largely repeats what the schema already documents. No significant additional param meaning is provided.

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 action: 'Create a new, exactly titled Firefox group from one or more ungrouped tabs in the same window, then verify every tab.' This clearly distinguishes it from sibling tools like list_firefox_tab_groups or move_firefox_tab_to_group.

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 (for creating a new group from ungrouped tabs) and notes that it fails if an exact group already exists. It does not explicitly name alternative tools, but the context is clear enough for an agent to decide.

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