get-screenshot

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

With no annotations, the description carries the burden of disclosing behavior. It clearly implies a read operation ('retrieve') and mentions polling, but does not describe error handling, return format, or whether the response is a status vs. image data. It is accurate but lacks depth for a tool with no output schema.

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 sentence that front-loads the core action and then adds usage context. Zero waste, every word 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 simple get-by-id operation, the description covers the action and usage, but with no output schema, it leaves the agent wondering about return values (e.g., does it return the image, a status, or a URL?) and error conditions. This is a meaningful gap for a polling tool, so it is merely adequate.

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 parameter is fully documented as 'The screenshot job ID to retrieve.' The description adds context about polling, but adds no extra meaning to the id parameter itself. Baseline of 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 specific verb ('Retrieve') and resource ('screenshot job'), and clarifies it is for polling async jobs or retrieving prior captures. This clearly distinguishes it from sibling creation tools like render-screenshot and capture-element.

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?

Explicitly tells when to use it (poll async jobs, retrieve previously captured screenshots), which gives clear context. It does not explicitly name alternatives or when-not-to-use, but the sibling names make the distinction obvious, so it earns a 4 rather than a 5.

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