set_keyframe

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

No annotations exist, so the full burden is on the description to disclose side effects (e.g., whether it overrides existing keyframes at the same time) or operational constraints. Description merely restates the action with no behavioral detail.

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?

Single short sentence, no unnecessary words. However, it is overly terse for a tool with 7 parameters and important constraints, which reduces utility.

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?

No output schema, 43% parameter coverage, no annotations. Description does not specify return behavior (e.g., success confirmation, errors), nor does it address the complex value types (number, array, object, string) beyond what the schema mentions. Incomplete for a 7-param animation tool.

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 covers 43% of parameters. The description repeats the schema's 'property' example but adds no extra meaning beyond it. Baseline of 3 is appropriate as schema partially documents time, value, and property, but the description fails to compensate for the other 57%.

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 states the verb 'Set' and the resource 'keyframe on a property', which is a specific animation action. It distinguishes from sibling tools like 'set_keyframe_advanced' and 'set_expression' but does not explain the exact difference.

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 explicit guidance on when to use this vs. alternatives like 'set_keyframe_advanced'. The description implies basic keyframing but fails to mention prerequisites (e.g., which layer/property must exist) or when to prefer other tools.

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