xr18_headamp_set_phantom

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

No annotations are provided, so the description carries the behavioral transparency burden. It does disclose an important guardrail: 'This requires confirm=true.' However, it does not mention consequences, error behavior when confirm is false, or the physical/irreversible nature of changing phantom power beyond the word 'physical'.

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 short sentences with no filler. The primary action is front-loaded and the confirmation requirement is stated immediately after, making the most important operational detail easy to spot.

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 tool with no annotations, no output schema, and two required parameters left unexplained, the description is too minimal. An agent would struggle to know what integer to pass for 'headamp' or what 'enabled' toggles, and there is no guidance on failure modes or return values.

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?

With 0% schema description coverage, the description must compensate for undocumented parameters. It only clarifies the confirm parameter ('requires confirm=true') and says nothing about what 'headamp' represents or how 'enabled' controls phantom power. Required parameters headamp and enabled remain effectively unexplained.

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 uses a specific verb ('Set') and a specific resource ('physical preamp phantom power'), which clearly identifies the tool's function. It is reasonably distinguishable from sibling tools like xr18_channel_set_fader or xr18_set, though it does not explicitly name alternatives.

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 description provides no guidance on when to use this tool versus alternatives such as xr18_set or channel-level fader/mute tools. The only usage-related instruction is 'requires confirm=true', which is a prerequisite rather than a when-to-use guideline.

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