mark_in_out

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

No annotations provided, so description carries burden. Explains clear behavior when no frames, but does not disclose side effects, destructive action, or output on read. Minimal but not misleading.

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 efficiently cover purpose and a key behavioral note. Could separate read/set/clear modes for clarity, but no wasted words.

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?

Lacks description of return values (how to read marks), error handling, or prerequisites. With 3 parameters and no output schema, description should explain what 'read' returns and how to invoke it.

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?

Schema has 0% description coverage. Description adds meaning for mark_type (video, audio, all) and explains clearing when both in_frame and out_frame are null. Does not clarify behavior when only one frame is set.

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?

Description clearly states the tool reads, sets, or clears timeline in/out marks, specifying the exact resource and actions. It distinguishes from sibling tools like marker_add, which deal with 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?

Provides one use case: calling with no frames clears marks. But lacks explicit when-to-use vs other marker tools (e.g., markers_get) and no alternatives mentioned. Implicitly distinguishes by 'in/out marks' concept.

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