chrome_save_page

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

With no annotations, the description must disclose behavioral traits, but it only states a high-level save action. It does not mention that the tool writes files to disk, how the 'selected tab' is identified, whether it requires an active CDP connection (debugUrl), or whether it blocks for page completion. This leaves the side effects and requirements largely opaque.

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, front-loaded sentence with no filler words. It is easy to read, though its brevity means important contextual details are omitted (but that is a completeness issue, not a conciseness issue).

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 9 parameters, no output schema, and zero schema description coverage, this description is far too sparse. It leaves the user without information on mandatory arguments, file naming, tab selection, or filtering behavior. For a tool of this complexity, the description is minimally viable at best.

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 9 parameters and zero descriptions, so the prose must compensate; instead it only hints at the html/pdf flags. The required outputDir, tabId/baseName selection, landscape print option, and urlContains/titleContains filters are never mentioned. The description adds little beyond the schema's property names.

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' with a clear resource 'selected Chrome tab' and specifies output formats ('HTML and/or PDF'). This makes the core purpose immediately understandable. However, it does not mention how this relates to sibling tools like chrome_snapshot or chrome_screenshot, so a user might not know when to prefer this tool.

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 usage guidance is provided. The description does not state when to use this tool versus alternatives like chrome_snapshot or chrome_eval, nor does it mention prerequisites such as a running Chrome instance or the debug port. There are no exclusions or conditions.

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