mxa_set_harm_sweep_dwell

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

The annotation 'destructiveHint: false' indicates it is not destructive, but the description adds no additional behavioral context. For a set operation, details about side effects, required states, or return behavior are missing. The description does not contradict annotations.

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 line), which is concise, but it lacks structure and useful orientation. It does not front-load critical info beyond the basic function.

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 tool's complexity (setting a specific instrument parameter with no required parameters and an output schema), the description is minimal. It provides no details on valid values, units, or expected effects, leaving the agent underinformed.

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%, so the description must explain parameters. It does not mention 'alias' (likely representing device alias) or 'params_json' (which presumably contains the dwell value). Without this, an agent cannot set the dwell time correctly.

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 purpose: setting harmonic sweep dwell time. It uses a specific verb 'set' and resource 'harmonic sweep dwell'. However, it does not differentiate from sibling tools like mxa_set_harm_sweep_auto or mxa_set_harm_bw.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or when to avoid it. Among many similar mxa_set_* tools, the agent has no basis for selecting this one.

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