cw_track_controls

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

With no annotations, the description carries the burden well: it discloses that the server only ships the contract and cannot read elements itself, and that actual access requires a computer-use runtime. The remaining gap is the shape of what comes back, though this is largely implied by 'the contract'.

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?

Three tight sentences, front-loaded with the what and followed by the capability caveat. The quoted element-naming example earns its place by making the contract concrete.

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?

For a zero-parameter contract/knowledge tool with no output schema, it covers purpose, applicability, and the hard limitation on who can act on the returned elements. A brief note on what the returned contract contains would close the last gap.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. No parameter-level detail is needed here.

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 resource and intent: reading and changing tracks via SONAR's accessibility tree, delivering element naming and per-strip controls. It is clearly distinct from direct setters like cw_set_track_volume, though it never explicitly says it is a reference/contract tool rather than an actor, which would sharpen the verb.

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?

Gives a concrete condition for use: builds with no CakeScript, driven from a computer-use runtime. It does not explicitly compare against siblings such as cw_ui_recipe or cw_get_track_control, so the agent must infer which one to reach for.

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