afg2125_set_function

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

Annotations do not indicate read-only or destructive behavior, and the description adds that this selection does not trigger auto-output, which is valuable behavioral context. It does not elaborate on other side effects but is sufficient for a simple function selector.

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 a single, front-loaded sentence with no filler words. It conveys the core action and a key behavioral distinction in under 15 words.

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 one-parameter waveform selection tool with an output schema, the description covers the purpose, the selectable values, and the no-auto-output behavior. It could mention exact input string syntax or prerequisites for user/ARB, but overall it is adequately 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 only defines 'function' as a string with no description or enum, and schema coverage is 0%. The description compensates by enumerating the selectable values (sine, square, ramp, noise, user/ARB), adding essential meaning to the parameter.

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 explicitly states the tool selects waveform functions including sine, square, ramp, noise, and user/ARB, and distinguishes itself from auto-output APPLy. This is a specific verb+resource+scope that clearly defines its purpose relative to siblings.

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 phrase 'without using auto-output APPLy' implies this tool should be used when the output should not be automatically enabled, providing useful usage context. However, it does not explicitly name alternative sibling tools or state 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.