save_pdf

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

With no annotations, description provides details on file naming, default directory, and return values. It adequately discloses behavior (download and save) without mentioning destructive actions or authentication, which is acceptable for a read-like operation. Slightly more context could be added, but overall strong.

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?

Concise yet comprehensive. Two paragraphs plus a bulleted return list. Front-loaded with core action and legal context. 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 only one parameter and an output schema (implied by the Returns section), the description covers all critical aspects: purpose, usage context, parameter details, and return values. No 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?

Despite 0% schema description coverage, the description thoroughly explains the directory parameter: default value (~/Downloads), auto-generated filename, and that the filename is set automatically. It adds significant meaning beyond the bare schema.

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?

Description clearly states action: 'Download the monthly consumption PDF and save it to disk.' It explains the document type (UVI, German statutory notice) and distinguishes from sibling tools by contrasting with 'just reading the structured consumption figures.'

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?

Explicit usage guidance: 'Use this tool when the user wants to save, view, or forward the actual PDF document rather than just reading the structured consumption figures.' Also notes the document covers the same month as get_last_available_month, providing context.

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