save_screenshots

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

The description goes beyond annotations (readOnlyHint) by detailing auto-recovery for clipped nodes, empty flag for blank renders, and format handling. It clearly explains what happens for each node case, which is very transparent.

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 a single paragraph with purpose front-loaded. It is detailed but not overly long. Minor redundancy could be trimmed, but overall efficient.

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 no output schema, the description explains the return structure well. It covers edge cases (missing, empty, recovered) and format nuances. However, it lacks explicit mention of input validation or error states, leaving minor gaps.

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?

With 100% schema coverage, the description adds significant meaning: scale only applies to raster formats, null path for unexportable nodes, recovered/empty flags, and naming convention. This is over baseline 3.

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 exports nodes and writes them to disk. It distinguishes from siblings like 'get_screenshot' which likely returns an image, and 'export_pdf' which exports to a different format. The verb 'Export' and resource 'nodes' are specific.

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 provides detailed behavior but does not explicitly state when to use this tool over alternatives like 'get_screenshot' or 'export_pdf'. There is no guidance on context or exclusions, leaving the agent to infer usage.

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