render_screenshot

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

With no annotations provided, the description carries the full behavioral burden. It does disclose the file-writing side effect and the tempfile default when save_path is omitted, but it does not mention overwrite behavior, return value, or prerequisites like whether the TOP must be cooked. This is adequate but has clear gaps.

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 short, scannable, and front-loaded with the main action. The inline type annotations are redundant with the schema, but the overall structure is efficient with no fluff.

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 tool, the description is enough to make a basic call. However, because there is no output schema, the missing return-path and overwrite details are notable, and the lack of differentiation from related rendering tools leaves the context incomplete.

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%, and the description compensates well by explaining both parameters: path is the TOP operator path and save_path is the output PNG path with a tempfile default. This adds meaning beyond the bare schema titles 'Path' and 'Save Path'.

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 and resource: saving a TOP's current frame to a PNG file. It is clear about the output format, but it does not explicitly distinguish this tool from siblings like render_export or bridge_snapshot, so it lacks direct sibling differentiation.

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?

There is no guidance on when to use render_screenshot versus alternatives such as render_export or node_snapshot. The description defines the inputs but gives no selection criteria, exclusions, or context for when this tool is the right choice.

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