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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false. The description adds valuable context beyond that: sandboxed Chromium rendering, default A4, 'Never overwrites an existing file', and refusal of remote assets and scripts. It explains why destructive page deletion is safe (writes to outputPath).

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?

Purpose is front-loaded and every clause carries information. It is a single dense sentence, which hurts scanability slightly, but there is little filler to cut.

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?

For a 12-parameter tool with nested objects and no output schema, the behavioral half is well covered (overwrite policy, sandbox, defaults), but the schema half is thin given 17% coverage – several parameters an agent must set (pages, format, pageSize, fontSize) are undocumented in both places.

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 only 17%, so the description carries most of the burden. It does an excellent job on the nested content operations (delete/insert, negative indices, markdown vs. sourcePdfPath) but leaves key top-level params unexplained: pages, format (text/markdown/html), pageSize, fontSize, fontPath, deviceId, workSessionId. Partial but significant compensation.

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 ('Create a PDF at path from Markdown content, or write an edited copy...') and distinguishes its two operating modes (creation vs. content-operation editing) with concrete syntax. An agent can identify the tool's scope without opening the schema.

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 two modes imply when each applies (create from Markdown, or edit to a new outputPath), but there is no explicit when-to-use/when-not guidance and no sibling named (write_file, edit_docx, copy_path are obvious alternatives). Usage is inferable rather than stated.

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