pdf_encrypt

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

Annotations are all false, and the description adds context: it reveals AES-256 encryption, default owner password behavior, and that a user password is required. It does not contradict annotations. However, it could mention that the original file is not modified (output to separate path) or any permission requirements.

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 is only two sentences, with no redundant information. It is front-loaded with the main action and efficiently conveys key details.

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?

Given the moderate complexity (4 parameters, no output schema), the description covers the main purpose and key behavioral aspects. It lacks details about error handling, prerequisites, or side effects, but is sufficient for most use cases.

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?

Input schema has 100% description coverage for all parameters. The description adds extra meaning by specifying AES-256 encryption and that ownerPassword defaults to userPassword. This goes beyond the schema's field descriptions.

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 encrypts a PDF with AES-256 password protection, specifying both user and owner password roles. It distinguishes from sibling tools like pdf_merge or pdf_split by focusing on encryption.

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 does not explicitly tell when to use or not use this tool compared to alternatives. While it implies use for password-protecting PDFs, it lacks guidance such as 'use for securing PDFs; for removing encryption, see pdf_decrypt' (not present in siblings). No alternative names are mentioned.

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