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

Annotations declare this is a non-read-only, non-idempotent, destructive, open-world call, so the safety burden is partly carried by structured data. Yet the description contradicts that framing by describing an innocuous 'capture' and adds nothing about billing, rate limits, or the 7-day result window that the schema hints at. No annotation contradiction in the strict sense, but the description undersells the operation.

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 tight sentence that front-loads the action. It is concise and readable, though it is under-specified rather than optimally concise.

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 tool whose parameter is an opaque nested object with 0% description coverage, the bare one-liner is not enough. It omits the prerequisite task flow, the fact that results are retrievable for 7 days, and any return-shape context despite an output schema existing.

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 reported at 0%, and the single nested 'body' parameter is not explained at all in the description. The agent must infer that task_id comes from a prior submit call, which is essential context the description omits.

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 names a specific verb ('capture a screenshot') and resource ('SERP page'), which is clearer than the generic name. However, it leans on the endpoint name rather than stating in its own words what the tool returns, and it does not distinguish this tool from any sibling.

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 when-to-use guidance, no prerequisites (e.g. that a task must first be submitted via a POST endpoint), and no mention of alternatives. The agent gets no routing help at all.

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