status

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

No annotations are provided, so the description carries the full behavioral burden. It discloses returned fields, clarifies that dirty means unsaved changes, and explains that detail=true adds arrangement facts, but it does not explicitly state read-only behavior, side effects, or error handling for a broken bridge.

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 front-loaded and dense: it states the core status check first, then usage guidance, then parameter behavior. Every sentence contributes useful information without unnecessary padding.

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?

With no annotations and no output schema, the description must explain enough about returned data, and it does list the key status fields and the extra detail fields. It could be more complete by specifying the default detail behavior or failure mode for an unavailable bridge, but it is sufficient for correct invocation.

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 0% for the single optional detail parameter, so the description must compensate. It does so by explaining that detail=true adds time signature, length in beats, markers, and per-track MIDI/audio facts, though it omits the default when detail is omitted.

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 a specific action, checking the Lua bridge, and enumerates exactly what state is returned: tempo, play state, tracks, any_solo, master_mute, and dirty. This makes its role distinct from sibling tools such as project, transport, and render.

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?

It gives clear usage context with 'Call first' and the prerequisite 'clear a lingering solo before rendering.' It does not name alternative tools or explain when not to use this one, but the operational guidance is specific.

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