animation_set_keyframe

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

Minimal disclosure beyond the action. Does not describe side effects (e.g., replacing existing keyframes), failure modes, or required state. With no annotations, the description should provide more behavioral context.

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?

Description is structured with a purpose statement and an Args list. It is reasonably concise, though the 'Category: Animation' line is extraneous. Overall efficient.

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?

Covers basic purpose and parameter meanings. Lacks preconditions (e.g., animation must exist) and behavioral details. Given the tool's complexity (6 required params) and presence of an output schema, it is adequate but not thorough.

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?

Since input schema has 0% description coverage, the description fully compensates by detailing each parameter (e.g., 'project_path: Path to the Godot project directory'). Provides clear semantics beyond the schema's titles and types.

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?

Clearly states 'Set a keyframe in an animation track' with specific verb (Set) and resource (keyframe in animation track). Distinguishes from sibling tools like animation_add_track and animation_create.

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 on when to use this tool versus alternatives. Does not mention prerequisites, such as the need for an existing animation or scene.

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