pdf_export

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

With no annotations, the description carries the burden of behavioral disclosure. It usefully discloses page format (A4), background setting, and the default output location ('data/screenshots'). It does not disclose how the optional save_path parameter affects behavior, whether the file is overwritten, or what the tool returns.

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 one sentence, tightly worded, and front-loaded with the action. Every element — current page, PDF, A4, backgrounds on, output location — earns its place.

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?

For a simple no-required-parameter tool, the description gives enough to make a basic call and expected the file under data/screenshots. However, the missing parameter semantics and lack of return/overwrite behavior keep it from being complete, especially because there are no annotations or output schema to fill the 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?

Schema description coverage is 0%, so the description must compensate for the undocumented save_path parameter. It only hints at the default destination and never explains how save_path should be formatted, whether it is a directory or full file path, or whether it overrides the default. This leaves significant ambiguity for the agent.

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 states a specific verb ('Save'), a specific resource ('the current page'), and a specific output format ('PDF'), with concrete constraints (A4, backgrounds on). This clearly separates it from sibling tools like screenshot by making the PDF output explicit.

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 intended use is implied: an agent should call this when a PDF of the current page is needed. However, the description does not explicitly contrast it with alternatives such as screenshot, and it does not state when not to use it.

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