get_clip_markers

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

No annotations are provided, so the description must disclose behavioral traits like side effects or permissions. It only states the basic operation without clarifying if markers include metadata or if it modifies state. As a read operation, it likely is safe, but this is not explicitly confirmed.

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 extremely concise, using two sentences to state purpose and parameter. The format with 'Args' is clean and front-loaded, with no redundant information.

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?

The tool has a simple signature with one required parameter and an output schema. The description adequately covers the parameter, and the output schema presumably documents return values. However, it does not mention that markers are from the current timeline, which is implied but could be clearer.

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 coverage is 0%, meaning no parameter descriptions in the schema. The description explains the parameter 'clip_name' as 'Name of the clip on the timeline,' adding meaningful context beyond the property name, but does not specify format or required characteristics.

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 explicitly states that the tool retrieves 'all markers' from 'a clip on the current timeline,' which clearly indicates the action and resource. It distinguishes itself from sibling tools like 'add_clip_marker' and 'delete_clip_marker' by specifying retrieval.

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 provides no guidance on when to use this tool versus alternatives, such as when to use 'get_timeline_markers' or how prerequisites like a loaded timeline or clip existence are handled. No context about exclusions or limitations is given.

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