arc_select_tab

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

Annotations already indicate non-read-only (readOnlyHint=false), and the description adds that it changes visible Arc state, which aligns. However, it does not disclose behavior on invalid IDs or other side effects. With annotations present, the description provides minimal extra value.

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?

Two sentences with no wasted words. The primary purpose is front-loaded: 'Select an Arc tab by explicit id.' The behavioral effect is succinctly appended. Ideal for quick comprehension.

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 simplicity (1 required param, no enums, output schema exists), the description covers the basic purpose and effect. However, it lacks usage context, such as when to choose this over arc_focus_space, and does not describe the output. Thus, minimally adequate.

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 lone parameter tab_id has 0% schema description coverage. The description mentions 'by explicit id' but does not explain what constitutes an id, its format, or how to obtain one. This leaves the agent underinformed about the parameter.

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 clearly states the tool selects an Arc tab by explicit id and that it changes visible state. This precisely defines the action and differentiates it from sibling tools like arc_analyze_tabs or arc_query_tabs.

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?

No guidance on when to use this tool vs alternatives (e.g., arc_focus_space, arc_get_tab). It doesn't mention prerequisites, conditions, or when not to use it, leaving the agent without decision context.

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