configure_sweep

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

Annotations only include readOnlyHint: false, indicating mutation. The description adds meaningful behavioral context by revealing the SWWV command construction and the dependency on state being ON first, which goes beyond the minimal annotation. No contradiction with 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?

Two concise sentences with no fluff. The purpose is front-loaded ('Configure sweep on a channel') and the second sentence delivers a critical usage constraint. Every word earns its place.

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?

Despite 24 parameters and no output schema, the description covers the most important non-obvious behaviors: the state ordering prerequisite and the command-building approach. The schema fully handles parameter details. Could potentially mention defaults or what gets overwritten, but overall sufficient for a configuration 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?

Input schema has 100% coverage with individual parameter descriptions, so baseline is 3. The description's phrase 'all specified parameters' adds no new parameter-specific meaning; the schema already documents each field thoroughly.

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 'Configure sweep on a channel' with a specific verb and resource, distinguishing it from sibling tools like get_sweep (read) and other configure_* tools. The second sentence about building a single SWWV command adds useful implementation-specific detail.

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 explicitly gives a usage ordering requirement: 'State must be set to ON before other parameters.' This is a clear directive for correct invocation. It does not explicitly name alternatives, but the tool's name and sibling set imply this is for configuring sweeps versus reading them via get_sweep.

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