screenshot_report_pages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers the best-effort caveat, fallback output mode, platform/dependency requirements, and the rendering_warnings signal. It doesn't mention file-write side effects or permissions, but the most non-obvious behavioral traits are honestly disclosed.

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 compact and front-loaded: a one-sentence purpose followed by the critical caveats in a second paragraph. There is no filler, repetition of schema fields, or irrelevant detail.

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?

The core behavior and fallback path are explained well, and an output schema exists so return-value details are less critical. However, the six parameters are semantically undocumented, and the description doesn't fully bridge that gap. It is a minimum-viable definition with meaningful missing context.

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 description adds essentially no parameter-level meaning. It does not explain pages, format, wait_ms, output_dir, resolution, or how they relate to the fallback behavior. With six parameters and no schema descriptions, this is a major gap.

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 opening sentence names a specific verb and resource: 'Best-effort screenshot capture of PBIR pages.' This clearly tells an agent what the tool does. It doesn't explicitly contrast with a sibling tool, but none of the listed siblings performs screenshot capture, so the scope is effectively unambiguous.

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 gives important context for when output is trustworthy: without the Power BI Desktop Bridge it produces SVG wireframes + JSON manifests, and real PNG/PDF requires superbi-mcp on Windows. It also signals a regression-diffing use case. It doesn't explicitly state exclusions or alternatives, but the prerequisites and degraded-output conditions are clear.

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