Write PDF

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is covered. The description adds useful context by disclosing the supported input formats and the insert/delete modify modes, but does not explain what delete operations affect, overwrite semantics, or auth/permission requirements beyond what the annotation implies.

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 with no filler; the create-vs-modify distinction is stated up front. It is efficient, though the bare enumeration could be marginally better structured.

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 complex tool that both creates and destructively modifies files with 6 parameters and no output schema, the one-line description is thin. It omits parameter guidance, output/return behavior, and the consequences of the destructive modify path, leaving significant gaps for an agent to call it correctly.

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 0% across 6 parameters, so the description must carry the load. It only hints at the 'content' parameter via the supported formats (markdown/HTML/CSS/SVG) and leaves path, options, deviceId, deviceName, and outputPath completely unexplained.

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+resource (create a PDF / modify an existing PDF) and enumerates supported input formats (markdown/HTML/CSS/SVG) plus the modify modes (insert/delete). This is clear and distinctive, though there is no explicit sibling differentiation, which is largely unnecessary given no other PDF tool appears in the sibling list.

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 says what the tool does but never states when to use it, when not to, prerequisites, or any alternative tool for overlapping tasks (e.g., write_file). An agent must infer usage entirely.

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