setLayerKeyframe

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

No annotations are provided, so the description bears full transparency burden. It only states the mutation ('set keyframe') but does not disclose whether existing keyframes are overwritten, if the property must already be keyframeable, or the effect of setting multiple keyframes at the same time.

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, front-loaded sentence with no wasted words. Every part is essential.

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?

With five parameters, no output schema, and no annotations, the description lacks crucial details: return value, behavior on duplicate keyframes, value formatting nuances, and error conditions. The tool's complexity demands more context.

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 100% (all five parameters documented). The description adds no additional meaning beyond the schema; it restates 'property' and 'time'. Baseline 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 uses a specific verb ('Set') and resource ('keyframe for a specific layer property at a given time'), clearly distinguishing it from sibling tools like 'setLayerExpression' (which sets expressions) or 'apply-effect' (which applies effects).

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 states when to use (to set a keyframe for a property at a time) but provides no explicit guidance on when not to use, prerequisites (e.g., layer must exist, property must be keyframeable), or alternatives among siblings.

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