show_mixer_status_card

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

With no annotations, the description must carry the full behavioral burden. It discloses that the tool returns a PrefabApp card with KPIs and uses data-testid attributes for testing, which is useful, but it does not state permissions, whether it connects live to hardware/software, or any side effects. For a read-only display tool this is adequate but incomplete.

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?

Short and front-loaded: the core action and display fields come first, followed by testing context and return type. The 'Returns' line is slightly redundant with the first sentence but still brief and informative.

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 simple status-card tool with no input parameters and no output schema, the description covers what is shown, how it is rendered, testing attributes, and the return type. It lacks sibling differentiation, but otherwise contains what an agent needs to call it correctly.

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 schema is already complete. The description correctly adds no parameter detail because there is none to add, matching the baseline for parameter-less tools.

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 'Show' and resource 'live mixer status', and lists exactly what is displayed (crossfader position, master gain, per-deck levels). It clearly differs from the deck-status sibling by resource, but does not explicitly name or rule out any alternative.

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 when-to-use, when-not-to-use, or alternative guidance is provided. The description only implies it is for viewing mixer status; it does not help an agent choose between this and show_deck_status_card or the mixx_mixer family.

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