pdf_decrypt

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

No annotations provided, so description carries full burden. It discloses that decryption needs password and saves an unencrypted copy (implies non-destructive to original). It does not mention error behavior for wrong password or permission requirements, but core behavior is transparent.

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?

Two sentences, no wasted words. The first sentence front-loads the core purpose. Every sentence earns its place.

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?

With 3 parameters and no output schema, the description is sufficient for a simple decryption tool. It covers what it does, prerequisites, and output. Minor gap: no mention of return value or error handling, but overall complete for the complexity.

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% with clear parameter descriptions. The description adds marginal value beyond the schema (e.g., confirming 'saves an unencrypted copy' aligns with outputPath). Baseline 3 is appropriate as description does not significantly enrich parameter meaning.

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 clearly states the tool removes password protection from an encrypted PDF, using specific verb 'remove' and resource 'password protection' + 'encrypted PDF'. It is distinct from sibling tools like pdf_compress or pdf_merge, which have different purposes.

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 explicitly states the prerequisite 'Requires the correct password' and the outcome 'saves an unencrypted copy'. However, it does not mention when to use alternatives (e.g., pdf_validate for checking encryption) or when not to use this tool.

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