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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is fully covered. The description adds only that the response is status/metadata (hinting at a non-content payload), with no detail on status values, polling behavior, or error cases for an unknown ID.

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?

One sentence, front-loaded with the verb and resource, no filler. Nothing could be trimmed without losing information.

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 no output schema, the description leaves the return shape and 'status' vocabulary unspecified, and it does not clarify the boundary with get_screenshot_result, which is the main ambiguity an agent faces among these siblings. Annotations cover safety, so the gap is scoped but real.

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 0% and the single 'id' parameter is documented only by a regex pattern. The description does add real meaning by saying the ID may be a capture ID or a job ID, which the schema does not convey, but it stops short of format or example guidance.

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?

States a specific verb and resource ('Get screenshot status and metadata') with the lookup key ('by capture or job ID'). The phrase 'status and metadata' implicitly separates it from get_screenshot_result, but it never names that sibling, so the distinction still requires inference.

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 'status and metadata' rather than stated: an agent can guess this is the polling/metadata call and get_screenshot_result is the content call, but there is no explicit when-to-use or when-not guidance, and the closest sibling is never mentioned.

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