generate_pdf

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

The description discloses key behaviors: it uses 'headless-browser HTML-to-PDF conversion' and 'writes it to the local reports directory,' revealing side effects beyond the annotations (readOnlyHint=false, destructiveHint=false). This adds useful context, though it doesn't mention file overwriting or return values.

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 sentence that front-loads the primary purpose, then adds technical details and output location. Every word is purposeful, and it avoids redundant restatement of the tool name or schema fields.

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 complex nested schema and no output schema, the description adequately covers the input source, rendering process, output format, and destination. It lacks explicit return-value or error-handling details, but for an agent selecting and invoking the tool, the essential context is present.

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 does not explain the parameters directly; it only references 'generate_report's schema.' With schema description coverage at 0%, the description fails to compensate for the lack of prose parameter explanations. The inline schema is thorough, but the description adds no parameter-specific meaning beyond a cross-reference.

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 function: 'Renders a structured report into an institutional-layout PDF' and specifies the output destination. It distinguishes itself from sibling tools like generate_markdown by the PDF output format and mentions generate_report's schema for input, which clarifies its role.

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 this tool: when an institutional-style PDF is needed, as opposed to markdown or a raw report. It doesn't explicitly state 'use this instead of X,' but the context of the PDF layout and mention of generate_report's schema gives clear guidance without exclusions.

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