anim-timeline

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

With no annotations, the description must convey safety and side effects. The verb 'Report' implies a read-only operation, but it does not explicitly state that no modifications occur. It also omits details about return format or units, leaving some behavioral ambiguity for an agent.

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, concise sentence that lists exactly what is reported. Every word adds value, and there is no fluff or redundancy. It is front-loaded and immediately informative.

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 simple report tool with no parameters and no output schema, the description covers the essential information: what data is returned. It is complete enough for an agent to understand the tool's function, though it could mention units or whether frames are 0-based or 1-based.

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 tool has no parameters, so the baseline is 4. The description adds no parameter-specific information, but none is needed. It correctly focuses on the tool's output rather than inputs.

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 tool reports scene timeline range, current frame, and frame rate, which is a specific, concrete action. It distinctly differentiates from sibling tools like anim-set_timeline and anim-set_frame, which perform mutations, and from anim-report, which likely provides a broader overview.

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 on when to use this tool versus alternatives. It does not mention scenarios like checking playback boundaries or frame position, nor does it contrast with anim-report or anim-keyframes. There is no context about appropriate use cases.

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