pdf_generate_report

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that a file is written and where ('output_path'), and that input can come from either inline JSON or a .json/.md file on disk, which is useful beyond the schema. It says nothing about overwriting existing files, required system dependencies, error behavior on bad paths, or output size, leaving material gaps for a file-creating mutation tool.

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?

A single front-loaded sentence that reads as a feature list ('Q&A cards, tables, images, callouts, code blocks, Turkish Unicode support'). Nothing is strictly wasted, but the enumeration crowds out the operational guidance an agent actually needs.

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?

Nine parameters, nested objects, no output schema, and no annotations make this a complex tool. The description outlines the visual output but omits the item-type contract referenced in sections, file-overwrite semantics, and sibling disambiguation, so it is only adequate for the complexity involved.

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 100%, so every parameter including nested section items is already documented. The description restates the input_file capability but adds no syntax, format, or structural detail beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Generate a ... PDF document') and enumerates the content it produces. It is not differentiated from the sibling pdf_from_markdown, even though it accepts '.md' input files, which creates real ambiguity about which tool handles markdown.

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?

No when-to-use or when-not-to-use guidance. With pdf_from_markdown as a sibling and this tool accepting .md input, the agent is given no rule for choosing between them, and no prerequisites or failure conditions are described.

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