create_keyframe_animation

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

Since no annotations are present, the description carries the full burden of disclosing behavioral traits. It omits any information about side effects, required permissions, or output behavior (e.g., whether the animation is applied instantly, returns an ID, etc.). This is insufficient for a tool that creates animations.

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 phrase that repeats the tool name. This is under-specification, not conciseness. Every sentence should earn its place; this one does not add value beyond the name.

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 (3 parameters, 2 required, no output schema, no annotations), the description is critically incomplete. It fails to explain the tool's purpose, how keyframes work, or what the output is. The description is inadequate for an agent to use 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?

The input schema covers 3 parameters with only 33% description coverage (only 'target' has a description in Chinese). The tool's description adds no parameter-level meaning beyond what the schema provides. For example, 'keyframes' expects an array of objects with progress and properties, but the description does not explain this structure or constraints. The baseline of 3 is lowered due to the low schema coverage.

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 '创建关键帧动画' is essentially a translation of the tool name, providing no additional purpose. It fails to differentiate from numerous sibling tools like create_timeline_animation or create_stagger_animation, all of which create animations. The description lacks a specific verb and resource context.

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?

No guidance is provided on when to use this tool versus alternatives. The description gives no context, prerequisites, or exclusions, leaving the agent to guess the appropriate scenario for keyframe animation creation.

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