tabs_create_mcp

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

Discloses that it creates a tab and returns data, and notes the cleanup expectation. Does not mention potential side effects like focus changes or prerequisites, but the core behavior is transparent.

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 somewhat verbose, mixing workflow instructions and cleanup policy into the tool definition. While structured and logical, it could be more concise by separating generic guidance from the tool's core purpose.

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?

Provides enough context for an agent to use the tool correctly, including what it returns (id and group contents) and its relationship to other tools. Lacks exact output format, but that is not critical given the absence of an output schema.

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?

No parameters exist, and the description correctly states 'It takes no arguments.' Baseline score of 4 applies for zero parameters.

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?

Clearly states the tool's action: open a new blank tab in the session tab group and report its id and the group's contents. Distinct from siblings like tabs_close_mcp and tabs_context_mcp.

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?

Explicitly instructs to call tabs_context_mcp first to know the group, then use navigate on the new tab id, and close it with tabs_close_mcp when no longer needed. Provides clear when-to-use and how-to-use guidance.

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