cw_get_track_control

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

With no annotations, the description carries the full burden; it does disclose that reads are accurate/current and that writes aren't possible here, which is useful. However it says nothing about failure behavior for an unknown label, label matching rules, or the format/precision of the returned 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 front-loaded sentences; the label example list earns its space by supplying the schema-missing vocabulary, and the write-scope caveat is the second thing the agent reads.

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?

No output schema and no annotations, yet the description never describes the return value (units, ranges, raw vs. normalized text) — a notable omission for a tool whose sole job is returning a value. Label discovery guidance is also absent.

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 coverage is 0%, so the description must compensate. The label examples (音量, 声像, 手动静音, 独奏...) give real vocabulary the schema lacks, but the meaning of 'index' (track index? 1-based?) and label matching semantics are never explained.

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?

States a specific verb and resource ('Read one track-strip control') plus a live-state qualifier ('as SONAR currently shows it'). It also distinguishes itself from the write-side siblings by naming cw_set_track_mute/solo/arm as the only writable controls.

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?

'Reading is accurate; writing is only available for the three toggles' clearly routes the agent to the setters when mutation is needed. It does not say how to discover valid labels (e.g., via cw_track_controls), so the agent may guess at label strings.

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