Markdown to PDF

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

The annotations declare readOnlyHint=true, but the description says the tool writes a result: the "output" parameter accepts "a file path, or a folder ending in '/'", with a default server output folder. Writing a PDF file modifies the environment, directly contradicting readOnlyHint=true. The rich feature and limitation disclosure otherwise adds useful context, but the annotation contradiction is serious.

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 dense and largely a single long feature list, but it is front-loaded with purpose and every clause describes relevant supported behavior or a limitation. For a 13-parameter conversion tool with no output schema, the length is defensible, though the run-on structure reduces readability.

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?

The description thoroughly covers input Markdown features and limitations, but with no output schema it does not clearly state what the tool returns by default beyond the optional base64 behavior. It also leaves the write-to-file behavior in tension with the readOnlyHint annotation, so an agent lacks a fully coherent behavioral picture.

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 high at 77%, so the schema already documents most parameters. The description adds marginal clarity by saying "Give 'markdown' inline or 'path' to a .md file" and by explaining unsupported-character behavior, but it largely repeats parameter meaning already present in the 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?

The description states a specific verb and resource: "Turn Markdown (GitHub-flavoured) into a clean, paginated A4/Letter/A5 PDF." It clearly identifies the output format and supported Markdown features, but it does not explicitly differentiate from sibling tools such as ai_markdown_to_docx or other PDF utilities.

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 implied usage by stating "Give 'markdown' inline or 'path' to a .md file" and lists important content limitations such as Latin-only text and remote images never being fetched. However, it does not say when to use this tool versus alternatives like ai_markdown_to_docx or other PDF tools, and it provides no explicit routing guidance.

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