ledfx_delete_qlc_event

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

The word 'permanently' indicates destructiveness, but no other behavioral details are provided (e.g., whether deletion is irreversible, if any confirmation is needed, side effects, or error states). With no annotations, more context would be helpful.

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?

Single sentence with no filler, effectively front-loaded with the action and object. Every word serves a purpose.

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?

Tool has a nested object parameter and no output schema. The description does not explain return behavior, error handling, or required knowledge about the event filter. Insufficient for a deletion operation that may have side effects.

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 three parameters with descriptions. The tool description adds no additional meaning beyond the schema, so baseline score of 3 applies. No elaboration on the 'event_filter' object structure.

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?

Description explicitly states 'Delete a QLC+ event mapping permanently', which includes a specific verb (delete) and resource (QLC+ event mapping). It clearly distinguishes from sibling tools like ledfx_create_qlc_event and ledfx_toggle_qlc_event.

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 on when to use this tool versus alternatives (e.g., ledfx_toggle_qlc_event or ledfx_create_qlc_event). Does not mention prerequisites or conditions for deletion.

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