Remove hidden information

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true), the description discloses non-obvious behavior: the original is never modified, an existing output file is only replaced with overwrite: true, and encrypted PDFs cannot be saved this way. These are exactly the failure modes an agent needs to know before calling a write 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?

Three sentences, no filler, front-loaded with the operation and the list of removed data, then routing to alternatives, then the mutation/encryption caveats. Every sentence carries distinct information.

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 4-parameter tool with no output schema, the description covers what is produced (a copy at the output path), what is left untouched, overwrite semantics, and the encryption limitation. An agent has everything needed to invoke it correctly and to anticipate failure conditions.

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 coverage is 100%, so the baseline is 3; the description nonetheless adds real meaning by tying overwrite to file replacement behavior and clarifying the encryption nuance — a password allows reading but not saving a new PDF. It reinforces rather than duplicates the schema, though it does not extend the path/output parameters.

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 ('Writes a copy of a PDF') and then enumerates precisely what hidden information is stripped: author, title, subject, keywords, creating program, dates, XMP, comment authors, edit leftovers, and photo location/camera data. This lets an agent distinguish it from every sibling, including the close ones (redact_pdf, get_pdf_info), without opening a 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?

Gives an explicit use case ('Use it before sharing a file') and names two alternatives with the condition that selects each: redact_pdf for visible text, get_pdf_info to only read the information. This is a complete when-to-use / when-not-to-use / alternative map.

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