set-effect-keyframe

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action without revealing side effects, how the tool resolves target properties (propertyPath vs propertyName vs propertyIndex), or what happens when keyframeIndex is omitted. For a mutation tool, this is a significant gap.

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 concise sentence that front-loads the core purpose and optional capabilities. Every word is meaningful, with no redundancy or filler.

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?

Given the tool's complexity (12 parameters, nested keyframeOptions), no output schema, and no annotations, the description is severely incomplete. It lacks workflow context, return behavior, or any explanation of how to effectively use the many parameters, leaving an agent without enough guidance to invoke the tool correctly.

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?

All 12 parameters have schema descriptions (100% coverage), so the baseline is 3. The description adds no parameter semantics beyond mentioning graph interpolation and easy-ease controls, which are already encapsulated in the keyframeOptions object. It does not explain parameter relationships or priority.

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 specific action 'Set an effect property keyframe' and mentions optional graph interpolation and easy-ease controls. This distinguishes it from sibling tools like set-effect-property (which sets without keyframing) and setLayerKeyframe (which targets layer properties rather than effect properties).

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 implies usage for animating effect properties over time, but provides no explicit guidance on when to use this tool versus alternatives such as setLayerKeyframe or set-effect-property. No exclusions or alternative tool names are mentioned.

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