ai.screenshot

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

The description mentions 'headless-browser' and 'returns base64 image + size metadata', but lacks details on error conditions, timeout behavior, or restrictions (e.g., JS-heavy pages). Without annotations, more context would help.

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 concise sentence with no redundant information, fitting front-loaded structure.

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 10 parameters and no output schema, the description is too sparse. It omits return format details beyond 'base64 + size metadata' and does not cover expected behavior for parameter variations.

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 low (30%), yet the description adds no parameter information. Many parameters have defaults and constraints not reiterated, so the agent must rely solely on schema descriptions which may be insufficient.

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 verb 'Take' and the resource 'headless-browser screenshot of a URL', which distinguishes it from sibling tools like ai.describe-image or url.render.

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 on when to use this tool versus alternatives. It does not mention prerequisites, limitations, or scenarios where other tools would be more appropriate.

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