save_pdf

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

No annotations are provided, so the description carries full burden. It discloses that the tool downloads and saves a file, with automatic filename generation. It does not cover potential side effects like overwriting existing files, required permissions, or network dependencies, but the core behavior is well described.

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 well-structured with a summary, context, usage guidance, parameter docs, and returns. It is front-loaded with the key action. While slightly verbose with legal details, every sentence adds value.

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 the tool's simplicity (one optional parameter, no annotations), the description covers legal context, relation to sibling tool, and alternative resource. It includes return fields. It does not mention error conditions or file overwrite behavior, but is fairly complete for its purpose.

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 description adds minimal meaning beyond the schema for the only parameter (directory). It repeats the default and adds that the filename is set automatically, but does not elaborate on constraints like valid directories or error handling. Since schema coverage is 0%, more detail would improve usability.

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 specific action: downloading and saving a PDF of the monthly consumption report. It identifies the document as the legally mandated UVI under German law, ties it to get_last_available_month, and distinguishes it from the resource alternative for reading/forwarding. This leaves no ambiguity about what the tool does.

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?

Explicitly states when to use this tool ('when the user explicitly wants the PDF saved to a local directory') and when not to ('use the resource ... instead'). Provides a clear alternative, making it easy for the agent to decide.

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