mxa_set_sweep_points

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

Annotations indicate non-destructive (destructiveHint=false), and the description implies a state-changing write operation. However, no additional behavioral traits are disclosed—e.g., whether it triggers a sweep, side effects, or required permissions. The description adds little beyond the annotation.

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 with no redundancy. It is front-loaded with the tool's action. However, it could benefit from additional structure (e.g., bullet points) but remains efficient.

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 has two parameters at 0% coverage and no behavioral details, the description is too sparse. It does not explain sweep points, default behavior, or output (though output schema exists). Operating context is missing, making the tool hard to use confidently.

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 description provides no explanation of the two parameters ('alias', 'params_json'). The agent cannot infer their purpose or format, making it difficult to correctly populate them.

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 states the tool sets sweep points ('设置扫描点数') for the MXA device. The verb 'set' and resource 'sweep points' are clear, but it does not distinguish from sibling setters like 'mxa_set_frequency' or provide context on what sweep points entail.

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 (e.g., other MXA setters). No prerequisites, conditions, or exclusions are mentioned, leaving the agent without context for correct invocation.

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