live12_browser_preview

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

No annotations are provided, so the description carries the full burden, yet it never says that preview produces audible output, whether it alters browser or transport state, whether hotswap monitoring is read-only, or what happens if stop is called when nothing is previewing.

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?

One front-loaded sentence with a compact parenthetical action list; nothing is wasted, though the parenthetical slightly duplicates the action enum.

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?

This is a simple two-parameter tool with fully described schema and no output schema, so little extra is needed. The key gap is the conditional dependency between action and browser_item_uri, which neither the description nor the schema's required list conveys.

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?

Schema description coverage is 100%: the enum values and the URI format are already documented in the schema. The description adds no parameter details beyond what it already provides, notably omitting that browser_item_uri is effectively required when action='preview'.

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 names a specific verb (controls) and resource (audio auditioning and hotswap monitoring in the Ableton Live 12 Browser) and enumerates its three actions. It is clear enough to separate it from load_item and browser_search, but it never explicitly says so.

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 parenthetical list of actions implies what the tool is for, but there is no guidance on when to reach for it instead of live12_browser_search or live12_browser_load_item, and no prerequisites or exclusions are given.

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