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

Annotations already declare readOnly, idempotent, non-destructive behavior, so safety needs no restating. Beyond that the description adds only 'recent', with no ordering guarantee, no indication of whether results are paginated or cursor-addressable, and no sense of how far back 'recent' reaches.

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 short sentence with the scope ('recent') front-loaded and no redundant restating of the tool name. Brevity here is efficient rather than padded.

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 list tool capped at 100 items with no output schema, an agent cannot tell what a returned capture looks like, in what order they arrive, or how to get older ones. The annotations cover safety, but the listing semantics an agent needs to call this correctly are missing.

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 has numeric bounds and a default for limit but no description text (0% coverage). The description clarifies that limit caps the number of returned captures rather than, say, a time window, which is modest added meaning.

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 clear verb and resource ('List ... bulk captures') with a recency scope, which is enough to know it returns a collection rather than a single item. However, it never differentiates from siblings such as get_bulk_capture or list_screenshots, so the boundary is left to inference from the tool name.

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 versus get_bulk_capture (fetch one by ID) or how to page beyond the cap. The phrase 'up to limit' hints at truncation but doesn't tell the agent what to do about it.

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