Remove a PDF password

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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false), so the bar is lower. The description adds genuinely useful behavior beyond them: it emphasizes local-only processing ('the file is read and written locally and never sent anywhere') and the known-password precondition. It omits what happens with the force/overwrite path, though the schema documents that.

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 short sentences, front-loaded with the core action and outcome, followed by the key exclusion and privacy note. Every sentence carries distinct value with no filler.

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?

No output schema exists, so the description must carry return semantics; it communicates the effect (a decrypted PDF written to the output path) implicitly but does not state the return value or success/error shape. Combined with the strong privacy and password-context notes, it is nearly complete for a simple file-transform tool.

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 all four parameters (input, output, password, force) are already documented in the schema. The description adds no additional syntax, format, or path semantics beyond that, so the 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 (decrypt) and resource (password-protected PDF), plus the outcome ('opens without prompting'). It is clearly distinguished from the inverse sibling pdf_protect.

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?

Explicitly rules out the main misuse case: it does NOT recover, guess, or brute-force forgotten passwords, and it requires knowing the password. It gives clear conditions for use but does not name an alternative tool (e.g., pdf_protect) for the opposite task.

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