blender_timeline

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

Annotations are all false and no output schema exists, so the description carries the full burden. It discloses that it can report and set values and manage markers, but does not mention side effects, reversibility, or what happens to existing data (e.g., when removing a marker). For a tool that can perform destructive operations like remove_marker, this is a significant omission.

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, efficient sentence that front-loads the core purpose and lists the affected resources. There is no filler. However, given the tool's complexity (multiple operations and parameters), it might be too terse, but structurally it is well-formed and easy to parse.

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 9 parameters, no annotations, and no output schema, the description is inadequate. It does not explain the semantics of each operation (e.g., what does 'set' do exactly? what happens on remove_marker?), nor does it describe return formats or any constraints. An agent would need to infer too much to call it 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 coverage is only 33%, so the description must compensate. It maps 'frame range' to start/end, 'fps' and 'step' to fps/step/fps_base, and 'manage markers' to op/name. However, it does not explain parameters like frame, response_format (though that has its own schema description), or the relationships between them. It adds partial meaning but not enough to fully cover the gap.

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 a specific verb-resource pair: report or set frame range, fps, step, and manage timeline markers. It is specific about what the tool does, but it does not explicitly differentiate from siblings like blender_set_frame or blender_animation_info, so it falls short 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?

No guidance is given on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or conditions for selecting specific operations. The description lists actions but provides no context for choosing between them or other timeline-related tools.

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