timeline_get

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It communicates that the tool returns current state, but it does not disclose whether the operation is purely read-only, what errors may occur, what output format to expect, or whether any side effects exist. There is no contradiction with annotations, but the disclosure is minimal.

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?

At six words, the description is extremely concise with no wasted content, and the core identifier is front-loaded. It is appropriately short for a simple getter, though it is a fragment rather than a complete sentence, so it does not earn a perfect 5.

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 getter with no output schema and no annotations, the description is minimally sufficient to indicate what the tool returns. However, given the large sibling set and lack of structured behavioral data, a clarifying sentence noting that this is a non-mutating read and describing the returned state would make it more complete.

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 and the empty input schema is fully covered by the structural data. The baseline for 0-parameter tools is 4, and there is no parameter information the description needs to add.

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 phrase 'Current timeline / playback state' clearly identifies what the tool exposes: a read-only snapshot of the current timeline/playback state. It is distinguishable from siblings like timeline_set, timeline_play, and timeline_pause, but it lacks an explicit verb and reads as a label rather than a complete sentence.

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 provided on when to use this tool versus related siblings (timeline_set, timeline_play, timeline_pause) or other getters. The intended usage is only implied by the tool name and the word 'current'. An agent is not told about prerequisites, such as whether playback must be running.

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