session_tabs

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

With no annotations, the description carries the full transparency burden. It states the prerequisite (`session_start`), the behavior of each operation, and the list fields (`id/url/title`). However, it does not mention side effects such as what happens to the active tab after `close`, whether `new` switches to the new tab, or behavior on invalid `tab_id`.

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 compact, front-loaded with the operation list, and has no boilerplate. Each clause maps directly to a parameter or behavior. The only stylized phrase ('as a human') is short and does not harm clarity.

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?

Given the tool's moderate complexity, the description covers the prerequisite, all operations, and the meaning of every relevant parameter. Since an output schema exists, the description need not restate return details. Minor gaps around invalid states and close/switch edge cases prevent a perfect score.

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?

The input schema provides zero parameter descriptions, so the description fully compensates. It defines legal `op` values, explains `url` semantics (URL or empty for a blank tab), and maps `tab_id` to both `switch` and `close`. This is exactly the guidance an agent needs to invoke the tool correctly.

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 precise resource (`session_tabs`) and enumerates the exact operations: `list`, `new`, `switch`, and `close`. The phrase 'Несколько вкладок — как у человека' clarifies this is multi-tab session management, distinguishing it from single-tab navigation/click siblings.

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 gives clear operational context: `op` selects the action, `url` is for new tabs, `tab_id` is for switch/close, and `session_start` is a prerequisite. It does not explicitly say when to prefer this over `session_navigate`, `session_links`, or `session_status`, but the action-by-action guidance is sufficient.

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