afg2125_set_fsk_enabled

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

The description adds the precondition that MAIN output must be disabled, but it does not disclose what happens if the tool is called when MAIN output is enabled (e.g., error, ignored) or any side effects on FSK configuration. Annotations are sparse, so the description carries the responsibility for behavior, which it only partially fulfills.

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, concise sentence that immediately conveys the action and the condition. No unnecessary words or repetition of schema details.

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-parameter toggle with an output schema, the description provides the essential information: what it does and the key precondition. It does not explain edge cases or returns, but given the simplicity and presence of an output schema, this is acceptable.

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 a single boolean parameter 'enabled' with no description (0% coverage). The description's 'Enable or disable' strongly implies that true enables and false disables, which is adequate for a simple boolean toggle, but it does not explicitly bind the parameter values to actions.

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 action ('Enable or disable FSK') and the specific resource ('FSK'), with a clarifying condition ('while MAIN output is disabled'). It is distinct from sibling tools like 'set_am_enabled' and 'set_fm_enabled' by naming FSK explicitly.

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 'while MAIN output is disabled' provides a clear context for when the tool should be used, implying that it is only applicable when the main output is off. However, it does not explicitly state when not to use it or mention alternatives, though the condition is a strong implicit guideline.

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