render_current_timeline

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

With no annotations, the description carries the burden of revealing behavior. It does disclose the explicit user approval requirement, which is a key behavioral trait. However, it leaves out what 'add a render job' concretely entails — e.g., whether the job is queued, how it interacts with start/user_approved, and what happens if approval is falsified.

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?

Two sentences with zero filler, each earning its place. The primary action is front-loaded and the critical constraint (approval) is placed immediately after, making the core behavior easy to scan.

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?

Given five parameters and no annotations, the description is too thin to be complete. It does not explain param roles, side effects of starting the render, or the expected flow, leaving an agent reliant on guesses about parameter interactions.

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 has 0% description coverage, and the description only implicitly references the user_approved parameter via the approval requirement. The other parameters (name, start, preset, output_dir) are left without added semantic meaning, so the description does not compensate for the low schema coverage.

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 action ('Add a render job') with a specific resource ('render job') and scope ('current timeline'). It doesn't explicitly distinguish itself from sibling tools like preview_timeline, but the verb+resource combination makes the core purpose clear even without direct comparison.

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 like preview_timeline or list_render_presets. The approval requirement is a constraint, but it does not help the agent decide between this and other timeline-relevant tools.

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