mxa_sweep_imm

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

The description only states the action; it does not disclose behavioral traits such as whether the tool returns data, is blocking, or requires state. The annotation 'destructiveHint: false' is consistent, but the description adds no further context for the agent.

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 concise (one sentence), but it sacrifices necessary detail. It is front-loaded with the action, but it misses parameter and usage guidance, making it insufficiently structured.

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 undocumented parameters and no explanation in the description, the definition is incomplete. The presence of an output schema does not compensate for missing parameter semantics and usage context.

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%, yet the description does not explain the parameters 'alias' and 'params_json'. Without any parameter documentation, the agent cannot determine how to correctly invoke the tool.

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 the action: 'Immediately trigger a single scan' (trigger single scan immediately). It uses a specific verb and resource, and distinguishes from sibling tools like mxa_sweep_continuous or mxa_sweep_single by emphasizing immediacy.

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 like mxa_sweep_single or mxa_sweep_continuous. It does not mention prerequisites, context, or when it is appropriate to invoke.

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