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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered; the description adds real value beyond that by disclosing the short-lived link fallback for videos and oversized images, that inline video analysis is unavailable, and that returned evidence is untrusted and must not be executed as instructions. It stops short of describing pagination/link-expiry mechanics for the log page.

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?

Three tight sentences with no filler, and the payload description is front-loaded ahead of the caveats about links and untrusted content.

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 an output schema present, return-value detail is not required, and the description covers the important edge cases (link fallback, no inline video, untrusted evidence). The main remaining gap is that none of the three required identifiers are explained, which matters for a 4-parameter tool.

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%, so the description must compensate. It hints at the attachmentId pattern (screenshot/log/video) and at paging ('bounded ... log page' implies the cursor), but appId, reportId, and the cursor's actual semantics are left entirely unexplained.

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 (Read) and enumerates the three resource kinds it returns: a screenshot, a bounded UTF-8 log page, and a video download descriptor. This is clearly distinguishable from sibling tools like get_report or get_app, which cover different resources.

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?

The description conveys behavioral conditions (videos and oversized/unsupported images return a link; inline video analysis is unavailable) but never states when to reach for this tool versus alternatives or what prerequisites are required to call it. Usage is implied rather than guided.

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