capture_screenshot

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

No annotations are supplied, so the description carries the full behavioral burden. It does not say whether a file is written to disk, what the default destination is, whether the call blocks, or whether the viewport is temporarily altered — all relevant for a capture operation with an output_path parameter.

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 zero filler. It is efficient, though the brevity comes at the cost of the behavioral and parameter detail noted elsewhere.

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 three undocumented parameters, no annotations, and no output schema, the description leaves too much unresolved: where the image goes, what settle_seconds does, and what is returned or confirmed. It is adequate only as a one-line summary of intent.

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 0%, so the three parameters (pane_name, output_path, settle_seconds) are undocumented anywhere. The phrase 'a specific pane tab' loosely gestures at pane_name, but output_path and especially settle_seconds — a non-obvious timing control — get no explanation, so the description does not compensate for the schema gap.

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 ('capture a screenshot') and scopes it to 'the viewport or a specific pane tab', so the agent knows exactly what operation is performed. It does not differentiate from the sibling 'capture_network_editor', which also appears to capture a screenshot-like artifact, so it stops short of a 5.

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 offers no when-to-use guidance, no exclusions, and no mention of alternatives such as capture_network_editor or compare_snapshots. The only implicit hint is the choice between viewport and pane tab, which is a parameter choice rather than usage guidance.

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