save_page_source

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

There are no annotations, so the description carries the full behavioral burden. It discloses the core file-writing side effect but says nothing about overwrite behavior, file destination semantics, whether the operation fails silently, or any permissions/path considerations.

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 clear sentence with no filler or repetition. It front-loads the core action and object, making it immediately scannable for an agent.

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?

The tool is simple, has no required parameters, and an output schema exists, so return values are covered. Still, the description lacks guidance on where files are saved, how name/folder interact, and when to prefer this over get_html_source, leaving the context only minimally complete.

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 does not mention either parameter. The schema only provides default values for name and folder, so the agent receives no explanation of what 'folder' means, how paths are resolved, or whether name should include an extension.

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 action ('save'), the resource ('current page's HTML source'), and the target ('a file'). This distinguishes it from siblings like get_html_source, which retrieves HTML, and save_screenshot/save_as_pdf, which save different formats.

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 implies when to use the tool: when the current page's HTML needs to be persisted to a file. However, it provides no explicit guidance about when not to use it or which sibling alternative might be better, such as get_html_source for in-memory retrieval.

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