delimit_screen_record

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

No annotations are provided, so the description bears the full burden. It discloses side effects: launches headless Chromium or terminal subprocess, writes MP4/GIF files under ~/.delimit/recordings/, gated by require_premium, and duration capped at 120s. This is comprehensive, though it could mention if files overwrite or if the operation is cancellable.

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 highly concise and well-structured with clear sections: purpose, when-to-use, when-not-to-use, sibling contrast, and side effects. Every sentence adds value without redundancy.

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?

Given the tool's complexity (screen recording with multiple modes and parameters) and presence of an output schema, the description covers input, side effects, output files, and usage constraints (Pro, duration cap). It is complete enough for an agent to determine when and how to invoke the tool.

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 coverage is 100%, so baseline is 3. The description adds context beyond the schema by explaining that script is for terminal mode only, and that there are two modes (browser/terminal). It also mentions file outputs per mode. This adds meaningful value for parameter understanding.

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 clearly states 'Record a screen capture' with a specific verb and resource. It distinguishes from sibling tool delimit_screenshot by noting it captures video over a duration, not a single still.

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?

Explicitly provides when to use (capture video for documentation, demo, audit) and when NOT to use (single still - use delimit_screenshot), giving clear context and alternative.

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