cmw_gen_load_arb

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

There are no annotations, so the description must carry the behavioral disclosure burden. It merely states 'Load ARB waveform file' without explaining side effects, error conditions, or whether it overwrites existing waveforms. No details about success/failure responses are provided.

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, well-structured sentence that is direct and front-loaded. Every word is meaningful, with no filler or redundancy.

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 tool has no annotations, no output schema, and a minimal 3-parameter schema, yet the description only gives a one-line summary. It lacks context about prerequisites, side effects, or relationship to other generator setup tools, making it incomplete for an agent to use safely.

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 only 33% (only file_path is described). The tool description does not explain any parameters, including the ambiguous host and port. It adds no meaning beyond the schema and fails to compensate for the low coverage.

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 'Load' the specific resource 'ARB waveform file' and the target 'CMW500 generator'. It is distinct from sibling tools like cmw_gen_configure_arb, which implies configuration rather than loading.

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 or prerequisites. There is no mention of required prior steps (e.g., connection) or how it relates to other generator tools like cmw_gen_configure_arb.

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