generate_dtmf

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

No annotations are provided, so the description carries the full burden. It explains that the tool fills the selected time range, which is useful behavioral context, but it does not disclose whether existing audio in the selection is overwritten, whether the operation is undoable, or what happens if no selection exists.

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: the primary action and selection requirement come first, followed by a concise parameter list. There is no filler or repetition of schema 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 low-complexity tool with three fully documented parameters and no output schema, the description covers the essential call semantics, including the selection prerequisite. It is slightly incomplete in not specifying valid DTMF characters in 'sequence' or clarifying whether generation replaces existing audio.

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 input schema provides only defaults and types, with no descriptions. The description fully compensates by explaining each parameter's meaning, valid range, and default: sequence text, duty cycle as tone/silence ratio, and amplitude as a 0-1 value.

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 and resource: 'Generate DTMF (telephone) tones' and adds the key scoping detail that it fills the currently selected time range. This clearly distinguishes it from sibling generation tools like generate_tone, generate_chirp, generate_noise, and generate_silence.

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 gives an explicit prerequisite: 'call select_region first to control duration.' This tells the agent when and how to use the tool acceptably, though it doesn't explicitly mention alternatives or when not to use it.

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