playwright_cli_save

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the operation (saving) but does not mention side effects (e.g., creating files on disk), prerequisites, whether the session needs to be active, or how the output is surfaced. This is a significant gap for a tool with no annotation safety hints.

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 11-word sentence, making it highly concise and front-loaded. It avoids verbosity, though the extreme brevity leaves out critical details. It earns its place but could be slightly more structured without losing efficiency.

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?

Despite having an output schema, the description is incomplete for a tool with six parameters and no annotations. It does not explain what 'current page' requires, what 'ref' refers to, or how session selection works. Given the tool's complexity, the single sentence is inadequate for an agent to select and invoke it correctly.

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 has 0% description coverage, so the description must compensate. It mentions 'screenshot or PDF' which loosely maps to the 'kind' parameter, but it does not explain any of the six parameters (ref, session, filename, max_chars, timeout_seconds). There is essentially no added meaning beyond what the raw parameter names imply.

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 uses a specific verb ('Save'), identifies the resources ('screenshot or PDF'), and scopes it to 'the current Playwright CLI page.' This clearly distinguishes it from sibling tools like open, goto, action, and snapshot, which serve different purposes.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention that it should be used after navigation or that it pairs with open/goto, nor does it exclude cases where snapshot or action would be more appropriate. The usage context is only implied by the phrase 'current page.'

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