watchface_raw_command

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

With no annotations, the description must fully disclose behavioral traits. It mentions 'enforced ReturnCode=0' but fails to cover error handling, side effects, authentication, rate limits, or idempotency. The lack of warnings about using a raw command is a significant gap.

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?

A single sentence that is front-loaded with the tool's purpose ('Raw POST /divoom_api command wrapper') and then immediately explains the key details. Every word earns its place; no 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?

Given the tool's raw nature and 17 siblings, the description lacks essential context: return values, error handling, command examples, and payload constraints. Users are left guessing, increasing risk of misuse.

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 low (33%), so the description should compensate. It clarifies that 'command' is required and 'payload' is merged with ReturnCode=0. However, it doesn't explain valid command values or payload structure, leaving much ambiguity.

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 it's a raw POST /divoom_api command wrapper, identifying the verb and resource. It distinguishes from sibling tools that are higher-level operations (e.g., watchface_set_brightness). However, 'raw' is vague and doesn't fully detail when to prefer this over alternatives.

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 explicit guidance on when to use this tool vs the many sibling tools. The description implies usage for arbitrary commands, but there's no mention of when not to use it or what alternatives exist. A dedicated 'when to use' section is missing.

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