pdf_encrypt

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

The description adds valuable technical context beyond annotations by specifying the RC4 128-bit algorithm and clarifying password semantics. However, it does not explicitly confirm the idempotent behavior declared in annotations or clarify that the source file remains unmodified (creating a new output file).

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?

The description consists of two tightly constructed sentences with zero waste. The first sentence establishes the core action and algorithm; the second explains the password hierarchy. Every word 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?

For a file transformation tool with 100% schema coverage and safety annotations, the description adequately covers the encryption behavior and password requirements. It could be improved by explicitly noting that the operation preserves the input file and whether running twice produces identical output.

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?

With 100% schema description coverage, the baseline is 3. The description reinforces the semantic distinction between userPassword (required to open) and ownerPassword (controls editing), but does not add critical syntax or format details beyond what the schema already provides.

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 the specific action ('Encrypt'), resource ('PDF'), and technical method ('RC4 128-bit'). The term 'encrypt' clearly distinguishes this from siblings like pdf_merge or pdf_extract_text, which handle different PDF operations.

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 provides clear guidance on the two password types (user vs. owner), explaining their distinct purposes for opening versus editing. While it does not explicitly name sibling alternatives, the encryption functionality is sufficiently distinct from other PDF tools that context is clear.

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