m8811_set_mode

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

The description adds behavioral context beyond the annotations by noting the output must be off and that DRM modes are 'guarded', hinting at a safety mechanism. Yet it does not explain what 'guarded' means, the role of confirm_drm, or the consequence of attempting with output on.

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 of 13 words, front-loaded with the action and object, containing 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 core function and a key constraint (output off) are present, but the description omits the meaning of 'guarded' DRM and the confirm_drm parameter. Given the safety-sensitive nature of the tool and sparse schema, this is a noticeable gap, though the output schema may cover return values.

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%, so the description must compensate. It covers 'mode' by listing valid values, but provides no explanation for 'confirm_drm' (a boolean with default false), leaving a required aspect of the tool's behavior unclear.

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 a specific verb ('Select') and identifies the resource ('mode'), enumerating the exact valid values (FIX, LIST, DRM/DRM0/DRM1/DRM2). This clearly distinguishes it from sibling tools like m8811_set_output or m8811_configure_list.

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?

It provides a clear precondition ('while output is off'), which implies when this tool should be used. However, it does not explicitly contrast with alternatives or state when not to use it, leaving usage guidance largely implicit.

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