ledfx_delete_effect_history

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

In the absence of annotations, the description explicitly notes that it clears the effect if currently active, which is a critical behavioral side effect. It could mention if the deletion is irreversible or requires certain permissions, but for a delete tool, this is adequate.

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 concise sentences, no fluff. The action and key detail about clearing if active are front-loaded, making it easy to scan.

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?

For a simple deletion tool with two parameters and no output schema, the description covers purpose, resource, and a key behavioral detail. It could mention that deletion is permanent, but that is reasonably implied. Overall complete for the tool's complexity.

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?

Both parameters have descriptions in the schema. The tool description does not add new meaning beyond restating 'effect type to remove from history'. Schema coverage is 100%, so baseline is 3; no extra semantic value provided.

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 the action (delete) and the specific resource (effect type from a virtual's effect history). It also mentions the side effect of clearing if active, which distinguishes it from other delete tools like delete_scene or delete_palette.

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 such as ledfx_clear_effect or ledfx_set_effect. The description only states what it does, not context like 'use when you want to permanently remove a specific effect type from history' or comparison to siblings.

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