get_markers

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

The verb 'Get' indicates a read-only operation, but with no annotations the description should ideally disclose prerequisites such as requiring an active sequence and what the returned markers include. It is minimally adequate but leaves meaningful behavioral details unstated.

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 with no wasted words, and the scope constraint appears before any optional 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 getter, the description gives enough context to select and invoke the tool correctly. The main remaining gap is that it does not describe the marker return structure, though the tool is simple enough that this is not critical.

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 there is no parameter semantics to explain; the schema already establishes that no input is required.

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?

States a specific verb and resource ('Get all markers') and scopes it to 'the active sequence', which clearly separates it from sibling tools like get_clip_markers.

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 active-sequence scope implicitly tells the agent when this tool is appropriate, but it never explicitly contrasts it with get_clip_markers or other marker tools, so selection guidance is only implied.

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