Delimit Screenshot

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

Beyond the annotations, it discloses concrete side effects: launching headless Chromium via Playwright, writing a PNG under ~/.delimit/screenshots/, and requiring a Pro license. It also describes the unlicensed failure response, which makes actual runtime behavior predictable.

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 labeled sections and the core action front-loaded. There is minor redundancy—'headless Chromium' appears twice and Pro is mentioned in both the opening and prerequisite—but every section earns its place.

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 two-parameter tool with an output schema, the description covers purpose, usage boundaries, sibling comparison, side effects, licensing prerequisite, and failure behavior. Nothing an agent needs to call it correctly 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 schema already documents url and name. The description adds context about the output artifact (a PNG file under ~/.delimit/screenshots/) but does not provide additional parameter-level meaning, so the baseline score of 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 concrete verb and resource: 'Take a screenshot of a URL using headless Chromium.' It also explicitly distinguishes itself from delimit_screen_record, so an agent can tell them apart despite the large sibling list.

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?

It provides explicit when-to-use scenarios (audit evidence, visual regression baselines, documentation captures) and explicit when-not-to-use cases (time-based recordings, rendered HTML extraction). For time-based recordings it names the alternative tool, delimit_screen_record.

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