ae_applyPreset

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is covered structurally. The description adds nothing behavioral beyond the name — it does not say whether existing keyframes/property values on the target layers are overwritten, what happens when a preset's properties don't exist on a layer, or whether third-party presets can fail to load.

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 well-formed sentence with the domain prefix and the key resource (.ffx) front-loaded; every clause earns its place. It is arguably too terse rather than too long, but there is no padding or 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?

For a state-mutating tool with no output schema, the description leaves out the essentials an agent needs to call it safely: path resolution format, whether target layers are overwritten, and expected failure modes for missing or incompatible preset files. Given the complexity of applying presets across layers, this is inadequate.

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 coverage is 67%: layers ('Layer names or 1-based indexes') and compositionName ('omit to use the active comp') are fully documented in the schema. The only undocumented parameter is `path`, and the description's '.ffx — including third-party preset packs' only loosely hints at its format without saying whether it is absolute, project-relative, or a preset name.

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?

Specific verb + resource + target: 'apply an animation preset (.ffx …) to layers', with the domain prefix 'After Effects'. It clearly differs from siblings like ae_addEffect or ae_applyExpressionTemplate by naming the .ffx preset concept, though it never names those alternatives explicitly.

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?

There is no guidance on when to use a preset versus ae_addEffect/ae_applyExpressionTemplate, and no stated prerequisites (preset file must exist on disk, path format, whether the comp/layers must already be open and selected). The agent must infer all of this.

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