pet_screenshot

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

No annotations are present, so the description carries full responsibility. It explains the scale parameter's behavior (nearest-neighbour upscale) and gives a usage tip. However, it does not mention where the screenshot is saved or any side effects, but the core behavior is 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 three sentences long, with the purpose front-loaded. Every sentence adds value: purpose, when to use, and parameter guidance. No wasted words.

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 low complexity (3 parameters, no output schema), the description covers the essential purpose and usage context. However, it omits explanation of the 'path' and 'session' parameters. Still, it is largely complete for typical use cases.

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 add meaning. It explains the 'scale' parameter and its recommended values, but does not describe the required 'path' parameter or the optional 'session' parameter. This partial coverage adds some value but leaves gaps.

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 tool saves a PNG screenshot, specifying the resource (PNG screenshot) and the verb (save). It also distinguishes from the sibling tool pet_screen_text by noting when to use each, making purpose very clear.

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?

Explicit guidance is provided: 'Prefer pet_screen_text for reading output; use this only when pixel-level appearance matters.' This tells the agent when to use this tool versus the alternative, fulfilling the usage guidelines dimension effectively.

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