set-effect-keyframe

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

No annotations are provided, so the description must fully disclose behavioral traits. It hints at graph interpolation but omits critical details like prerequisite (effect must exist and property must be keyframable), the effect of overwriting existing keyframes, or whether the action is destructive. This lack of transparency 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, front-loaded sentence that conveys the core purpose efficiently. However, it could be slightly expanded with contextual details without losing conciseness.

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 objects, no output schema), the description is too brief. It does not cover prerequisites, return values, or typical use cases, leaving significant gaps for an agent to understand proper invocation.

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 parameter descriptions are already present. The tool description adds no additional meaning beyond stating 'optional graph interpolation and easy-ease controls', which is already captured in the schema. Baseline score of 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 clearly specifies the action ('Set'), the resource ('effect property keyframe'), and the optional features ('graph interpolation and easy-ease controls'). It effectively distinguishes this tool from siblings like 'set-effect-property' which sets values without keyframing, and 'setLayerKeyframe' which targets layer-level keyframes.

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 does not provide explicit guidance on when to use this tool versus alternatives, such as using 'set-effect-property' for non-keyframed values. Usage is implied by the term 'keyframe', but no when-not or alternative references are given.

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