Get screenshot

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

No annotations, so description carries full burden. Explains that variant is ignored for sections, how full variant delivers in segments with iteration, and that section slugs capture the section. Does not cover error cases or rate limits, but sufficiently covers key behavior.

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 main purpose, then details. No wasted words. Could be slightly more structured (e.g., bullet points for variants) but overall efficient and readable.

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?

Given the tool's complexity and lack of output schema, the description covers the main use cases and parameter behavior. It warns about tall captures and iterating segments. Adequate for an agent to use correctly.

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 schema already documents parameters. Description adds meaning: explains what each variant does, clarifies that variant is only for pages, and that segment is used for tall captures. Adds context beyond schema.

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?

Clearly states it returns a screenshot image of a page or section. Distinguishes between pages (with variants) and sections. The verb 'returns' and resource 'screenshot image' are specific. No sibling overlap mentioned but the purpose is distinct from other tools.

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?

Tells when to use: to see the design. Explains pages vs sections and variant choices. But does not explicitly say when not to use or mention alternatives from sibling list. The advice to view references before designing is helpful context.

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