tab_create

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

Annotations already declare the write behavior with readOnlyHint=false, destructiveHint=false, and idempotentHint=false. The description adds that the tab starts with one shell pane and returns the new tab and root_pane ids, but it does not describe side effects such as focus behavior or workspace defaults.

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 two short sentences with the creation purpose front-loaded and the return value noted immediately after. Every sentence adds useful information without redundancy.

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 annotations cover the safety profile and an output schema exists, but the description leaves all four parameters unexplained despite 0% schema coverage. For a create tool with workspace, label, cwd, and focus options, this is incomplete.

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?

There are four parameters (cwd, focus, label, workspace_id) with 0% schema description coverage, and the description does not mention any of them. An agent gets no explanation of what these optional inputs control beyond their bare schema titles.

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: create a tab, and adds the default scope that it contains one shell pane. It is clear enough to distinguish this from tab_list/tab_focus/tab_close by name, but it does not explicitly route against sibling tools such as pane_split.

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 only states what the tool does; it gives no guidance on when to use this tool versus alternatives such as pane_split or workspace_create. There are no exclusions, prerequisites, or contextual triggers.

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