setEffectKeyframes

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

No annotations are present, so the description must carry the full burden. It mentions batching and efficiency but does not disclose behaviors like whether existing keyframes are overwritten, how targets are resolved, or error handling. This is insufficient for a mutation operation.

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 sentences, front-loaded with the primary action. No redundant wording; every word earns its place.

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 complexity of 7 parameters including a nested keyframe structure, the description provides minimal high-level context. It does not explain the relationship between name/index selectors or the keyframe array structure, though the schema does. The lack of annotations and output schema leaves the description insufficient for a fully fluent agent.

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 descriptions cover all parameters (100%), so the baseline is 3. The description adds no additional parameter semantics beyond what is already in the schema, such as clarifications on property paths or selection by index vs 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?

The description specifies the exact action (set multiple keyframes) and target (effect properties), using a clear verb and resource. It differentiates from siblings like setLayerKeyframes by explicitly mentioning 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 phrase 'More efficient for animating effects' implies use for batch effect animation, but it does not explicitly discuss alternatives or when not to use it. No exclusion criteria are provided, so guidance is only implied.

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