mxa_preset

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

The description mentions that it clears all current settings and measurement data, which aligns with the destructiveHint=true annotation. It adds some context about what gets destroyed but does not disclose other behavioral traits like irreversibility or authentication needs. With annotations already indicating destruction, the description adds marginal value.

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 sentence that efficiently conveys the tool's main purpose and effect. Every word is necessary, and the key information is front-loaded.

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 destructive preset action, the description covers the essential effect. However, the lack of parameter documentation and explanation of return values (even though an output schema exists) leaves gaps. The tool is minimally complete but fails to fully inform the agent.

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 input schema has two parameters (alias and params_json) with no descriptions, and schema description coverage is 0%. The description does not mention these parameters at all, providing no guidance on their meaning or usage. The agent cannot determine how to fill them 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 resets the instrument to a preset state and clears all settings and measurement data. It uses a specific verb ('恢复' restore) and resource ('仪器' instrument), and the MXA prefix distinguishes it from sibling tools like cmw_preset or ps_preset.

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 implies usage when a preset is needed but does not explicitly provide when-to-use vs alternatives or when not to use. No exclusions or alternative tool names are mentioned, leaving the agent to infer context from the tool name alone.

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