anim.timeline

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

Without annotations, the description carries full burden. It describes the tool as reporting data (timeline range, current frame, frame rate), which implies a read-only, non-destructive operation. This is clear and sufficient for a simple tool with no parameters. However, it does not mention any required scene state or output format.

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 that conveys all necessary information. No unnecessary words or repetition. It is appropriately concise.

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 tool with no parameters and no output schema, the description is complete. It lists the three pieces of information reported (timeline range, current frame, frame rate). No additional context is needed given the tool's simplicity.

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?

There are no parameters, and schema description coverage is 100% by default. The baseline for 0 parameters is 4. The description does not need to add parameter semantics since none exist.

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's action: 'Report scene timeline range, current frame, and frame rate'. It uses a specific verb ('Report') and resource ('scene timeline'). The name 'anim.timeline' and description distinguish it from sibling tools like 'anim.set_timeline' (which modifies) and 'anim.set_frame' (which sets frame).

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 implies usage for reading timeline information, but it does not explicitly state when to use this tool versus alternatives like 'anim.set_timeline'. No guidance on prerequisites or exclusions is provided, though the context of 'report' suggests read-only use.

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