decrypt

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

No annotations are provided, so the description carries the full burden. It states the tool removes the password but does not disclose whether it creates a new file, overwrites the original, or what happens on an incorrect password. The output_name parameter suggests a new file, but the description doesn't confirm this behavior or any side effects.

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 a single concise sentence that directly states the tool's purpose with no wasted words. It is appropriately sized for a straightforward decryption operation.

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?

Despite having 3 parameters and no output schema, the description is too sparse. It omits important context such as output file behavior, default naming, error handling, and whether the original file is modified. This leaves significant gaps for an agent to understand the full scope of the 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 descriptions cover all 3 parameters (file, password, output_name) with clear meanings, so the baseline is 3. The description adds no additional parameter information 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 uses a specific verb 'Decrypt' with a clear resource 'password-protected PDF' and states the outcome '(removes password)'. It distinguishes itself from siblings like encrypt or remove_restrictions by explicitly focusing on password-based decryption.

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?

Usage is implied: use when a PDF is password-protected. However, there is no explicit when-to-use or alternative/exclusion guidance, such as differentiating from remove_restrictions or change_permissions. The agent must infer the appropriate context from the name.

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