cmw_apply_template

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

There are no annotations, so the description carries the full burden of disclosing side effects. It merely says 'apply' without mentioning what settings change, whether the operation is reversible, or what happens if no template is loaded. The mutation-like nature is implied but not described.

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 sentence with no redundant words, so it is concise. However, it is under-specified and lacks any structural elements like separate purpose, prerequisites, or effects, making it only 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?

With two parameters, no output schema, and numerous related tools (cmw_connect, cmw_load_template), the description is incomplete. It does not explain when a template is considered 'currently loaded,' what applying accomplishes, or how host/port relate to the operation, 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?

The input schema defines only host (string) and port (integer) with zero descriptions, and schema description coverage is 0%. The description does not mention these parameters at all, providing no clue as to their purpose (presumably connection details) or format, making it impossible to fill 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 uses the verb 'apply' and specifies the resource as 'currently loaded template' targeted at the CMW500. It distinguishes itself from sibling cmw_load_template by implying an existing loaded template. However, it does not clarify what 'apply' entails, so it stops short of being fully specific.

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 such as cmw_load_template, cmw_load_state, or direct configuration tools. It also omits prerequisites like having a template loaded or a connection established, leaving the agent without orientation.

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