ledfx_apply_global_effect

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

No annotations; minimal disclosure. Does not explain side effects (e.g., overwriting existing effects), behavior on invalid virtuals, or fallback parameter meaning beyond the schema.

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?

Two sentences with no redundancy; front-loaded action and scope. Every sentence adds unique 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?

Missing return behavior, error handling, and fallback explanation. Given 4 parameters, nested objects, and no output schema, the description is too brief.

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 covers all 4 parameters with descriptions (100% coverage). Description adds no extra parameter context beyond 'bulk' application.

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?

States verb 'apply', resource 'effect type and config to multiple virtuals', and explicitly mentions 'Bulk effect application', differentiating from single-virtual tools like ledfx_set_effect.

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?

Implies usage for applying effects to multiple virtuals at once but lacks explicit when-to-use, when-not-to-use, or comparisons to siblings like ledfx_apply_preset or ledfx_apply_global.

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