Remove or toggle an effect

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

The description clarifies the two modes of operation—removing versus disabling—which goes beyond the bare annotations. However, it does not state whether deletion is reversible, what happens if the effect does not exist, or how the tool behaves with invalid targets. With annotations only indicating mutable behavior, this is acceptable but not rich.

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 efficient sentence that conveys the primary action and its alternative. It is front-loaded and contains no filler, though 'just switch it off' is slightly informal and could be clearer.

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?

Even with no output schema, the mutation-only nature of the tool is straightforward, and the schema fills in the selection/omission rules for comp and layer. The description adds enough context for a basic invocation, but could improve by mentioning behavior around selections and invalid effect names.

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 100%, so the schema already documents all parameters. The description's pointer to 'switch it off' maps to disableOnly but does not add meaning beyond the parameter documentation. Baseline 3 is appropriate.

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 explicitly states a specific verb ('Delete') and resource ('an effect from a layer'), and names the alternate behavior ('switch it off'). This distinguishes it from siblings like ae_apply_effect, ae_search_effects, and ae_remove_keyframes without needing to inspect their schemas.

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?

The description provides no guidance on when to choose this tool over alternatives, nor does it mention any exclusions or preconditions. An agent cannot tell from the description whether ae_remove_keyframes would be more appropriate for a given task, or when disableOnly should be preferred over deletion.

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