screenshot

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

With no annotations, the description carries the behavioral burden. It clearly communicates that the tool writes an image file in PNG/BMP/JPG format, which is useful, but it does not mention preconditions (e.g., whether a document must be open), overwrite behavior, or whether the viewport is altered.

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 conveys the tool's purpose and key format options without wasted words. Every element earns its place.

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 one-parameter, no-output-schema tool, the description covers the subject matter, rendering style, and file formats. The only notable omissions are explicit prerequisites and side-effect details, but the tool is simple enough that this is an acceptable gap.

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 coverage is 0%, so the description must compensate. The verb 'Save' and the listed formats imply that 'path' is the destination file path, and the format list adds some meaning beyond the bare 'Path' property. However, the description never explicitly states how the path relates to format selection or file creation.

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 states a specific action ('Save'), a precise rendering style ('isometric, zoom-to-fit'), and the target resource ('current part or assembly'). Naming the supported image formats clarifies it as a screenshot capture tool, which differentiates it from the 'export' sibling.

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 makes the usage context clear: when an isometric, zoom-to-fit image of the current part or assembly is needed. It does not explicitly state when not to use it or mention 'export' as an alternative, so it stops short of a full 5.

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