save_pdf

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

With no annotations, the description carries full responsibility for behavioral disclosure. It goes beyond the name by revealing the tool is a no-op/stub that will fail, explains why (Firefox cannot use Playwright PDF generation), and why it still exists (API compatibility). This is excellent transparency.

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?

Three concise sentences, each earning its place: the action, the environment limitation, and the alternative. The warning is properly front-loaded after the one-line summary, and there is no filler.

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 deliberately disabled compatibility stub, the description is nearly complete: it tells the agent the tool fails, why it fails, and what to use instead. The only gap is that it does not specify the exact failure behavior (e.g., thrown error or empty result), but 'fails by design' is sufficient for practical use.

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 'path' parameter. It does not mention what 'path' does, whether it is ignored, or what value should be passed. Since the tool is a compatibility stub this is somewhat mitigated, but no semantic meaning is added.

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 tool's intended action: 'Save page as PDF.' It also explicitly explains that this tool is non-functional in this environment and is kept only for API compatibility, which makes the actual purpose unmistakable. It names the alternative, screenshot(full_page=true), distinguishing it from a relevant sibling.

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 gives explicit when-not-to-use guidance: save_pdf fails by design because Camoufox is Firefox, and directs the agent to use screenshot(full_page=true) instead. This is a model example of routing to the correct alternative.

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