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

Annotations already indicate readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: it discloses that the binary PNG is NOT inlined and that only byte-length and metadata are returned. This is important for an agent deciding whether the tool output will satisfy its need.

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 with no filler: the first states the action and key return caveat, the second gives a compact example. The most important behavioral constraint is front-loaded, and every sentence earns its place.

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 read-only screenshot tool with full schema coverage and helpful annotations, the description is largely complete. It covers the essential caveat about binary data not being inlined. It does not describe the exact metadata fields returned, but since there is no output schema, a bit more detail could help; still, the agent has enough to invoke 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 description coverage is 100%, so the schema fully documents all five parameters. The description adds a concrete example using url, fullPage, and _apiKey, but does not explain semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 specific verb and resource: 'Capture a screenshot of a rendered page.' It also clarifies the return behavior (byte-length and metadata only), which distinguishes it from sibling content/scrape tools. The example reinforces the exact call shape.

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?

Usage is implied by the tool name and description: use this when you need a rendered screenshot. However, it does not explicitly mention when to prefer browserless_content, browserless_scrape, or browserless_smart_scrape, nor any exclusions. The example provides a concrete invocation but no decision guidance.

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