cmw_load_template

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention that loading a template modifies instrument state, requires a connection, or how errors are handled. The only behavioral detail (parameter key rejection) is in the schema, not the description.

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 two sentences, front-loaded with the action, and contains no redundant or filler text. Every sentence contributes useful information.

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 is adequate for a simple template loader but lacks behavioral context around side effects, prerequisites, or failure modes. Since there is no output schema or annotations, more detail would be expected, but the complete parameter schema and the reference to cmw_list_templates partially compensate.

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?

All three parameters have schema descriptions, so the baseline is 3. The description reinforces that presets and valid parameter names can be found via cmw_list_templates, but this is already present in the schema. It adds no new meaning beyond what the schema provides.

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 tool loads a measurement template by name, optionally with a preset. The verb 'load' and resource 'measurement template' are specific, and the reference to cmw_list_templates helps distinguish this from sibling tools like cmw_apply_template.

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 directs users to call cmw_list_templates to discover presets and valid parameter names, which is clear contextual guidance. It does not explicitly state when not to use this tool or mention alternatives, but the guidance provided is actionable and relevant.

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