safari_screenshot

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

Discloses that the tool is expensive and produces base64 JPEG. However, lacks details on whether it captures viewport or full page by default, or side effects. The parameter fullPage adds some clarity.

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?

Two sentences, front-loaded with purpose and efficiency warning. 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?

For a simple tool with one boolean parameter and no output schema, the description covers purpose, usage guidance, and parameter meaning sufficiently for correct agent invocation.

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% with the fullPage parameter described as 'Capture full page (not just viewport)'. The description adds no extra meaning beyond the schema, so baseline 3.

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 'Take a visual screenshot (base64 JPEG)', specifying the action and output format. It distinguishes from sibling safari_snapshot by noting it is expensive and for layout verification.

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 advises using safari_snapshot instead for most tasks and specifies when to use screenshot: 'Only use screenshot when you need to verify visual layout, styling, images, or colors that snapshot can't show'.

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