browser_save_image

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

No annotations provided, so description bears full burden. It comprehensively details output_path behavior (directory, file, error conditions) and return value structure (status, saved_path, size_bytes). Every aspect of the tool's 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 longer but well-structured with bullet points for output_path behavior. Every sentence adds value; however, minor redundancy (e.g., 'Args:' formatting) could be trimmed. Still efficient for the amount of detail.

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 2 parameters, one required, and presence of output schema (implied by 'Returns:'), the description fully covers input handling, output behavior, and return values. No gaps in information for an agent to correctly invoke the tool.

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% with empty parameter descriptions. The description adds full semantic meaning: screenshot_json_str_or_file is JSON from browser_screenshot or file path; output_path behavior with three cases. This fully compensates for the missing schema descriptions.

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 'Save base64 screenshot data to PNG file.' It specifies the verb (save), resource (screenshot data), and output format (PNG). It distinguishes from siblings like browser_screenshot which captures the screenshot, making its purpose unambiguous.

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 explicitly mentions that input comes from browser_screenshot tool, and details the behavior of output_path. While it doesn't name alternative tools, the context shows it's the complementary save tool, and no sibling has overlapping functionality.

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