mhs5200_configure_sweep

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

While annotations indicate the tool is not read-only, the description contains an internal contradiction: it states this tool only sets parameters, but the Returns section says 'JSON confirming sweep configuration and start.' This implies the tool might start the sweep, conflicting with the instruction to use `mhs5200_set_sweep` for start/stop. Such inconsistency lowers transparency.

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 concise, front-loaded with the purpose, and includes structured `Args` and `Returns` sections. However, the contradiction in the Returns section detracts from clarity, preventing a perfect score.

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 description provides enough context to use the tool alongside its siblings, but it omits details about error handling, parameter validation, or behavior when sweep is already configured. The internal contradiction also reduces completeness.

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 already provides descriptions for each parameter. The tool description's `Args` block repeats this information without adding significant new meaning (e.g., constraints like min/max are already in schema). Therefore, the description offers marginal extra value beyond the schema, meeting the baseline.

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 'Set sweep parameters for a channel' with a specific verb and resource. It explicitly distinguishes from the sibling tool `mhs5200_set_sweep`, which is used to start/stop the sweep, making the tool's role clear.

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 provides explicit guidance: 'Use mhs5200_set_sweep to start/stop the configured sweep.' This tells the agent when to use this tool (for configuration) and when to use an alternative (for execution), fulfilling the dimension well.

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