arb_set_phase

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

There are no annotations, so the description carries full behavioral disclosure burden. It only says 'set the phase' and lists parameters; it does not describe side effects, whether the output must be enabled, or error behavior.

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 compact: one action sentence and a minimal two-item Args list. No filler or repetition; every line contributes information.

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 two-parameter setter, the core call semantics are adequately defined. However, without annotations or usage guidance, the agent lacks context about side effects and when to choose this tool versus related setters, so it is not fully complete.

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 schema provides only property names/types with no descriptions, so the description compensates by explaining that channel is 1 or 2 and phase is in degrees. This is essential for correct invocation, though it could add ranges or interaction details.

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 exactly what it does: sets the phase in degrees on the waveform generator. The resource and action are specific, and the phase focus clearly separates it from sibling tools like arb_set_frequency or arb_set_amplitude.

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 guidance is provided. It does not mention alternatives or cases where another arb_set_* tool would be more appropriate, leaving the agent to infer usage from the tool name alone.

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