mxa_set_frequency

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

Only destructiveHint=false is annotated. The description adds no extra behavioral details such as side effects, required instrument state, or error conditions. It does not disclose whether the tool resets other settings or requires prior configuration.

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 very short (one short phrase), which is concise but sacrifices necessary detail. It lacks structure (no parameter descriptions, no usage hints).

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?

Given the low schema coverage and lack of usage guidance, the description is incomplete. An output schema exists but is not described; the description should at least mention that results are returned. Sibling context suggests this is part of a larger MXA toolset, but the description does not connect to that context.

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%. The description does not explain the two parameters ('alias', 'params_json') at all. With no info in the description, the agent cannot infer how to structure the input, making this a critical gap.

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: 'Set center frequency and frequency sweep width' (translated from Chinese). It specifies the verb and resource, but does not explicitly differentiate from sibling tools like mxa_set_freq_start_stop or mxa_query_frequency.

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?

No guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when to prefer this over related tools like mxa_set_freq_start_stop.

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