blender_keyframe_channel

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

Annotations already mark this as a non-read-only, non-idempotent, non-destructive operation. The description adds meaningful behavior beyond that: it can target any RNA data path including modifiers and custom properties, and it can fill a whole frame range. This helps the agent predict scope and side effects without contradicting the annotations.

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 two sentences with no filler. The primary action is front-loaded, key capabilities are named immediately, and the comparison to the original tool is both useful and compact.

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?

For a 9-parameter tool with no output schema, the description gives enough high-level orientation for selection: it states the action, scope, and range-fill option. The remaining gaps, such as exact sibling tool name and return format, are minor because the schema and the strong first sentence cover most invocation needs.

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 description coverage is only 56%, and the description only conceptually maps to data_path and frame_end. It reinforces that 'any data path' includes modifier levels and custom properties, and that frame ranges are supported, but it does not clarify step, group, index, or object semantics beyond what the schema already provides.

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 opens with a specific verb and resource: 'Insert keyframes on any data path', and immediately expands the scope with concrete examples like modifier levels and custom properties. It also explicitly distinguishes itself from the original keyframe tool, which only handled the three standard transforms, so an agent can tell it apart from blender_insert_keyframe.

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 comparison to the original keyframe tool gives clear context: this tool is for broader data paths and frame-range filling, while the original was limited to standard transforms. It does not explicitly name the sibling tool or state a when-not-to-use condition, so it falls just short of fully explicit routing.

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