arb_set_pm

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

Annotations are absent, so the description carries full responsibility for behavioral disclosure. It only says "Enable PM" and does not mention whether enabling PM disables other modulation modes, whether output must be enabled, or any side effects.

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 and front-loaded with the purpose, followed by a clean Args list. It contains no filler or redundant content.

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 instrument command, the intent and parameter semantics are present, and an output schema exists. However, it lacks usage context, valid numeric ranges, and interaction with other modulation settings, so the agent is left to make some assumptions.

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 coverage is 0%, but the description compensates by adding meaning to all three parameters: channel range (1 or 2), deviation unit (degrees), and frequency unit (Hz). It does not provide valid numeric ranges, but it gives the essential semantics needed to invoke the tool.

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 "Enable PM (phase) modulation on the waveform generator," which is a specific verb and resource. The parenthetical disambiguates PM as phase modulation, differentiating it from sibling AM/FM modulation tools.

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 guidance is given about when to use this tool versus alternatives such as arb_set_am, arb_set_fm, or arb_disable_modulation. Usage must be inferred from the tool name and description alone.

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