blender_keyframe_list

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

No annotations are provided, so the description carries the full burden of explaining behavior. It only says 'List all keyframes for an object,' which implies a read-only operation but does not disclose return structure, scope of 'all keyframes,' or any edge behavior. There is no contradiction, but the behavioral context is minimal.

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 short and front-loaded, with no filler words. It is appropriately concise for a single-parameter listing tool, though its brevity leaves some semantic gaps that other dimensions already penalize.

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?

With no output schema and no annotations, the description should explain what the returned keyframe list looks like and what 'all keyframes' includes. It does neither, leaving an agent uncertain about return values, scope, or how keyframes are grouped. This is insufficient for a tool with no structured return information.

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 schema already documents the single parameter ('Name of the object') with 100% coverage, so the baseline is 3. The description adds little beyond restating that keyframes are tied to an object, but it does not provide any extra detail like object naming conventions or how missing objects are handled.

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 a clear verb ('list') and resource ('all keyframes for an object'), so an agent can tell this is a read operation on keyframes. It does not explicitly distinguish itself from siblings like blender_action_list or blender_keyframe_insert, but the verb and target are unambiguous enough.

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 description gives no guidance about when to use this tool versus alternatives such as blender_action_list, blender_keyframe_insert, or blender_keyframe_delete. There is no stated context, prerequisites, or exclusions, so the agent must infer usage from the tool name alone.

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