configure_am_tone

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

Annotations cover safety profile, and the description adds substantial behavior: it uses analog AM path 1, disables ARB/IQ and competing modulation, documents rate/depth ranges, states RF stays OFF unless rf_on=True, and clarifies that stored voice waveforms are not altered.

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 with purpose, then adds constraints and side effects in four short sentences. Every sentence provides useful operational context without rephrasing the name or title.

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 5-parameter mutation tool with no output schema, the description covers side effects, ranges, RF default behavior, and persistence limits well. However, missing semantics for the required frequency_hz and level_dbm parameters leaves a notable gap.

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%, so the description must carry parameter meaning. It documents rate (0.1–50000 Hz), depth (0.1–100%), and rf_on behavior, but omits frequency_hz and level_dbm, both of which are required parameters.

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 and resource: configure ordinary sine-tone AM with adjustable front-panel depth. It distinguishes itself from voice playback and from stored waveform operations, and identifies the analog AM path and disabled competing modes.

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?

Clearly implies when to use it: to replace voice playback with a sine tone without altering the stored voice waveform. It does not explicitly route the agent among siblings like set_am_depth or play_waveform, but the operational context is clear.

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