afg2125_set_fm_enabled

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

Annotations indicate readOnlyHint=false and destructiveHint=false, consistent with a state-changing toggle. The description adds value beyond annotations by revealing the condition that MAIN output must be disabled, which is a meaningful behavioral constraint not captured in the structured data.

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, well-structured sentence with no redundant words. It front-loads the action and resource, then adds the conditional context efficiently.

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 one-boolean-parameter toggle, the description is largely sufficient. It mentions the key prerequisite (MAIN output disabled) and, given the output schema exists, does not need to detail return values. It could mention prerequisite configuration (e.g., calling afg2125_configure_fm first) but this is not essential.

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 has 0% coverage for the 'enabled' parameter, but the description 'Enable or disable FM' directly maps to the boolean semantics (true enables, false disables). While not explicit about the mapping, it is implied and clear from the tool name and description.

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 clearly states the tool's function: enabling or disabling FM, with a specific condition (while MAIN output is disabled). It clearly distinguishes this from sibling tools like afg2125_set_am_enabled and afg2125_set_fsk_enabled, making the resource and action unambiguous.

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 provides clear context by indicating the precondition that MAIN output must be disabled. However, it does not explicitly mention alternatives or when not to use this tool, though the name and sibling set make the FM-specific nature obvious.

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