Delimit Screen Record

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

The description discloses concrete side effects: launching headless Chromium or a terminal subprocess, writing MP4/GIF files to ~/.delimit/recordings/, gating on require_premium, and returning an upgrade error without running when unlicensed. Annotations only provide readOnlyHint=false and destructiveHint=false, so this description adds substantial behavioral context that the annotations do not convey.

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 well-structured with clear headers, front-loaded purpose, and useful side-effect and prerequisite sections. It is slightly longer than necessary because the 'When NOT to use' and 'Sibling contrast' sections partially overlap, but every section still contributes actionable 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?

For a tool with optional parameters, a Pro licensing prerequisite, file-output side effects, and an output schema, the description covers the prerequisite, the failure behavior, output locations, duration cap, and sibling differentiation. Nothing an agent needs to decide whether and how to invoke it is missing.

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 description coverage is 100%, so the input schema already documents all five parameters with defaults and constraints. The description reinforces the 120-second cap and browser/terminal modes, but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a specific verb and resource: 'Record a screen capture (browser or terminal session)'. It clearly identifies this as a duration-bound recording tool and contrasts it directly with delimit_screenshot, making the tool's identity and scope unambiguous.

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 explicit 'When to use' and 'When NOT to use' guidance, including naming delimit_screenshot as the alternative for still images. This gives an agent a clear decision rule for selecting this tool over its closest sibling.

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