Screenshot a report

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

Annotations already declare it a safe read operation (readOnlyHint=true, destructiveHint=false). The description adds real value beyond that by specifying the render mode ('view mode') and the output artifact ('PNG'), which matters since no output schema exists. It omits any auth or timing context, keeping it just short of 5.

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 front-loaded sentence with no filler; the core action and its scope arrive first.

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 simple two-parameter read tool with no output schema, the description conveys the return format (PNG) and the render mode, which is the essential missing piece. Nothing critical for invoking it correctly is absent.

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 100%; both page and report_id are documented in the schema, including the 1-based default and the URL-acceptance behavior. The description adds no parameter detail beyond what the schema already states, so the baseline 3 applies.

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: capture a PNG of a report page. The 'in view mode' qualifier narrows the action meaningfully. No sibling tool does anything similar (run_query, list_reports, build_report_link), so no differentiation is strictly needed.

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?

'to check charts after editing' implies a usage context, but it is a purpose rationale rather than explicit when-to-use guidance. There is no mention of when not to use it or which alternative to pick for other verification needs.

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