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

With no annotations, the description bears full responsibility for behavioral disclosure. It only states 'Screenshot of any public URL (viewport PNG)', omitting details about viewport size, load time, error handling, rate limits, or whether authenticated pages work. 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, front-loaded sentence that communicates the core purpose without extraneous words. It could be slightly more informative (e.g., 'returns a viewport PNG image') without losing conciseness.

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?

With no output schema and no annotations, the description is the sole source of context. It does not explain the return format (beyond 'PNG'), possible errors, or how the tool interacts with sibling tools like 'url_safety'. For a tool with 1 parameter and no technical metadata, more guidance is expected to complete the agent's understanding.

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% (no param descriptions provided), so the description must compensate. It adds the constraint that the URL must be 'public', which is meaningful but minimal. It does not specify expected URL format, protocol support, or what happens with non-public URLs. Baseline 3 is appropriate given partial compensation.

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 the tool captures a screenshot of any public URL and outputs a viewport PNG. The verb and resource are unambiguous. However, it does not differentiate from sibling tools like 'read' or 'url_safety', which could be used for retrieving content from URLs.

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 (e.g., 'read' for text extraction or 'url_safety' for checking URLs). There are no prerequisites, restrictions, or examples of appropriate use cases.

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