screenshot-pdf

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

With no annotations, the description carries the full behavioral burden, yet it says nothing about the return type (image bytes, URL, base64), required permissions, rate limits, or whether rendering large pages is expensive. Only the 0-indexing convention and PDF support are disclosed.

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 compact sentence with the operation front-loaded and the key constraint (0-indexed, PDF support) parenthetically noted. No filler, though the phrasing 'page pageno' is slightly awkward.

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?

No output schema and no annotations means the description should explain what a screenshot call returns and any page-state preconditions, but it omits both. An agent cannot tell whether the result is an image blob or a link, nor how ref_id is obtained.

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%, so both pageno (0-indexed) and ref_id (PDF URL or reference ID) are already fully documented in the schema. The description restates the same facts rather than adding format examples or constraints, so 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 states a concrete verb (take a screenshot) and a specific resource scope (a single PDF page identified by ref_id or URL). It distinguishes the operation from generic page tools by noting it works on PDFs, though it does not name which sibling to prefer.

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?

There is no guidance on when to choose this over siblings like open-page, fetch, or find-in-page, nor any prerequisite (e.g., must the PDF be opened/fetched first, where does ref_id come from). Usage must be inferred entirely.

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