mxa_sweep_single

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

The description says 'execute' and 'wait for completion', which implies a state change (write operation), but annotations set readOnlyHint=true, indicating a read-only operation. This contradiction misleads the agent. The description does not disclose blocking behavior, timeouts, or error handling.

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 very short (one line), which is concise but lacks essential structure. It contains no explicit sections or detail, making it minimally acceptable.

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 performs a complex action (sweep with parameters, blocking behavior) and has many siblings, the description is too sparse. It does not mention parameter semantics, output schema, or usage context, leaving critical gaps.

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 does not explain the two parameters ('alias' and 'params_json'). Their purpose, allowed values, and format are completely unspecified, leaving the agent unable to use 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 it executes a single sweep and waits for completion, distinguishing it from siblings like mxa_sweep_continuous (continuous sweep) and mxa_sweep_imm (immediate sweep). The verb 'execute' and resource 'single sweep' are specific, though the meaning of 'single sweep' in context could be elaborated.

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 no guidance on when to use this tool versus alternatives. It does not mention when-not to use it or reference any sibling tools. The user must infer usage 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.