screenshot

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

With no annotations, the description carries the behavioral burden. It states the core output (saves PNG, returns path) and the intended use, but it does not clarify what include_image=false actually changes about the response or whether files persist/overwrite. That leaves some behavior implicit, though not misleading.

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?

Two sentences, zero filler, and the most important instruction is front-loaded. Every clause contributes either the action or the usage constraint.

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 single-optional-parameter tool with no output schema, the description covers the action, return type, and routing. It lacks explicit details about include_image=false behavior and possible side effects of saving a file, but these are minor for a simple screenshot operation.

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 schema provides only name/default with 0% description coverage, so the description must compensate. It does by explaining when to set include_image=true ('only when visual inspection is necessary') and when to avoid the tool. It could be stronger by specifying the effect on the returned payload, but it provides a usable decision rule.

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 opens with a specific verb and resource: 'Save a display PNG and return its path.' This clearly differentiates the tool from sibling data-acquisition tools like get_waveform and measure, which pull numeric traces rather than images.

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?

It gives an explicit decision rule: set include_image=true only for visual inspection, otherwise prefer measure/get_waveform. This tells an agent exactly when to call this tool versus named alternatives.

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