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

The description adds useful behavior beyond annotations: it notes the URL must be public, the full_page behavior, and the return of a file_id and a ~1h download URL. While annotations provide openWorldHint and non-destructive hints, the description enriches with operational details without contradiction.

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 two sentences with zero redundancy. The primary action is front-loaded, and the optional parameter and return format are clearly mentioned. Every word contributes to understanding, making it highly efficient.

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 two parameters and no output schema, the description covers the core behavior, the optional full_page parameter, and the return payload (file_id and download URL). It does not address error handling or edge cases, but for the tool's simplicity, the information is sufficient.

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 coverage is 100%, with descriptions for both parameters. The description echoes the schema's parameter descriptions (e.g., 'Set full_page for the entire scroll height') without adding new semantic meaning. It does not go beyond what the schema already provides, so the baseline 3 applies.

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's function: 'Fetch a public http/https URL and capture a PNG screenshot.' This specifies the verb (capture), the resource (URL), and the output format (PNG), distinguishing it from siblings like url_to_pdf (PDF) and read_url (text content).

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 explicit guidance on when to use this tool versus alternatives. The description does not mention sibling tools or conditions for selection. It only states the action and the full_page option, leaving the agent to infer when a screenshot is preferred over PDF or text extraction.

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