blender_keyframe_insert

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

With no annotations provided, the description must disclose behavioral traits. It says 'optionally setting its value' but does not explain side effects like whether existing keyframes are overwritten, how frame defaults work, or any requirements for data_path. The mutation implication is clear but under-specified.

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, front-loaded sentence with zero filler, which is excellent for conciseness. However, it is so brief that it sacrifices context, making it less structurally complete than a 5.

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?

The tool has 5 parameters including a Blender-specific data_path, but the description only hints at the action and value. It doesn't explain proper property paths, frame handling, or the expected behavior of the index parameter. Without an output schema and with no annotations, an agent would need external knowledge to use this 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?

Schema description coverage is 100%, so all parameters are documented in the schema. The description adds only a minor reinforcement of the value parameter, but does not clarify format or interaction between parameters beyond what the schema already states. Baseline 3 applies.

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 clearly states the action ('Insert a keyframe') and the resource ('for an object property'), with an optional value-setting capability. It distinguishes from keyframe deletion and listing tools by its verb, but does not explicitly contrast with siblings, so it misses the full definition of a 5.

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?

There is no guidance on when to use this tool versus the deletion or listing keyframe tools, nor any mention of prerequisites like object existence or animation context. The agent must infer usage from the tool's name and schema alone.

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