timeline_get_info

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

With no annotations, the description carries the full burden, and 'Get ... info' clearly communicates a read-only operation with no mutation or destructive side effects. It also discloses the scope of data returned. It does not explicitly say 'does not modify the timeline,' but the verb choice and info framing make that safe behavior evident.

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?

A single front-loaded sentence states the verb and resource, then a compact colon-led list enumerates all returned categories. There is no filler, repetition, or irrelevant detail.

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 zero-parameter info-getter with an output schema, the description fully covers what an agent needs to know: what the tool is for and what data it returns. The output schema handles the detailed return-value shape, and the listed categories match the complex scope of timeline state.

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 zero parameters, so the baseline is 4. There are no parameter semantics to document, and the description correctly avoids inventing any.

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 uses a specific verb ('Get') and resource ('timeline info') and enumerates the distinct data groups (tracks+clips, duration, position, zoom, guides, markers, profile). This clearly distinguishes it from sibling tools like timeline_get_duration, timeline_get_position, and timeline_get_zoom by positioning it as the comprehensive aggregate.

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?

While it does not explicitly name alternatives or say 'use this when you need multiple values,' the word 'comprehensive' plus the explicit inclusion of duration, position, and zoom strongly signals this is the umbrella info tool versus the narrower single-purpose getters. The context is clear, though exclusions are not stated.

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