game_screenshot

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

Annotations are minimal (only title), so the description carries the burden. It discloses that the tool returns a base64 PNG, but does not mention any side effects (e.g., whether it pauses the game, captures overlays, or has performance impact). The behavior is largely self-evident for a screenshot utility.

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, complete sentence that is front-loaded and contains no extraneous words. Every element (verb, resource, output type) is essential and well-ordered.

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?

Given the tool's simplicity (no parameters, no output schema), the description covers the essential purpose and output. It could optionally mention resolution or behavior during scene transitions, but it is sufficiently complete for a screenshot capture.

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?

The input schema has zero parameters with 100% coverage. The description does not need to explain parameters. It adds value by clarifying the return format, which is beyond what the schema provides.

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 description clearly states the action ('Screenshot') and the resource ('the running game'), with no ambiguity. It also specifies the output format (base64 PNG), which is explicit and distinguishes it from other tools that might capture screen content differently.

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 explicit usage guidelines or comparisons to alternatives are provided. However, for a straightforward screenshot tool, the context is implied as capturing the game's current visual state. The lack of guidance does not critically hinder usage, but it's not proactive.

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