mxa_set_attenuation

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

Annotations already indicate destructiveHint=false, and the description ('set input attenuator') implies a non-destructive configuration change. The description adds no further behavioral details such as side effects, prerequisites, or rate limits, offering minimal value beyond the 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 extremely brief (one phrase), which is concise but lacks structure. It does not front-load key information or organize details. The brevity is acceptable but the content is insufficient.

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?

The tool has two generic parameters and an output schema, but the description is a single line. It fails to explain how to use the parameters or interpret results. The description is incomplete for an agent to reliably invoke this tool.

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%, and the tool description does not explain the purpose or format of the two parameters ('alias' and 'params_json'). The agent is left without any guidance on what values to provide, making correct invocation unlikely.

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 '[MXA] 设置输入衰减器' clearly indicates the tool sets the input attenuator for an MXA instrument. The verb 'set' and resource 'input attenuator' are specific, and the tool is distinguishable from sibling MXA commands like mxa_set_frequency and mxa_set_rbw.

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 usage guidance is provided. The description does not specify when to use this tool versus alternatives such as cmw_set_input_attenuation or other MXA set commands. The agent receives no context about prerequisites or appropriate scenarios.

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