capture_responsive_screenshots

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions capturing screenshots but does not disclose any side effects, output format, whether multiple viewports are captured, or any permissions/requirements. This leaves significant behavioral ambiguity.

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 a single, focused sentence that starts with the action and is free of unnecessary words. It is appropriately sized, though minimally so.

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 no output schema and no annotations, the description should explain what the output looks like (e.g., image paths, URLs) and any relevant context (e.g., viewport sizes). The description only states the action, leaving the tool incomplete from a usability perspective.

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?

The schema describes the pathname parameter with a default and pattern, but the description provides zero parameter information. Since schema description coverage is 0%, the description should have compensated by explaining what pathname refers to (e.g., 'specify the pathname of the page to screenshot'), but it does not.

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 uses a specific verb+resource ('Capture responsive screenshots') and indicates the target ('an internal page'), making the primary action clear. However, it does not differentiate from sibling tools like inspect_page or run_visual_analysis, which might also involve screenshots.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks context about whether this should be used for responsive design checks, visual regression, or other scenarios, and no exclusions or alternative recommendations are mentioned.

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