show_view

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

No annotations are provided, and the description doesn't disclose side effects, such as whether this changes the current UI state, requires the view to exist, or returns visibility status. The verb 'show' implies a state change, but no behavioral context is given beyond the name.

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 concise, with a one-sentence summary and a compact Args block. No wasted words, and examples are integrated efficiently.

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?

While the tool is simple and has an output schema (reducing the need to explain return values), the description leaves ambiguity about its effect (visible state vs. switching focus) and lacks usage context among sibling view tools. Given the low complexity, it's minimally viable but not fully complete.

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 description adds meaning to the sole 'view_name' parameter by listing example values like 'Browser', 'Arranger', 'Session', and 'Detail/DeviceChain'. This compensates for the schema's 0% description coverage, though it doesn't provide an exhaustive enum.

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 'Show an Ableton UI view' with a specific verb and resource. It provides examples of view names, clarifying the resource type. However, it doesn't differentiate from siblings like 'focus_view' or 'is_view_visible', so it's clear but not fully distinguishing.

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. The description doesn't mention hide_view, focus_view, or is_view_visible, nor does it state whether it's for switching the active view or only for showing.

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