Remove a PDF password

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

Beyond the annotations, the description discloses that the password is sent to the Paperless instance over its API and warns to use it only on a controlled instance. However, it does not explain side effects of delete_original, update_document, or include_metadata, nor what happens to the original file after decryption.

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 with no wasted words, front-loaded with the action and purpose, followed by a relevant security note. 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 no output schema and five parameters, the description omits the semantics of the three boolean parameters and the post-decryption flow. An agent cannot infer when to set update_document or delete_original or what response to expect, leaving significant gaps for correct invocation.

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 only 20%; only 'documents' has a schema description. The description adds meaning for 'password' (sent over the API to the instance), but it leaves delete_original, update_document, and include_metadata entirely unexplained, failing to compensate for the low coverage.

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 'Decrypt password-protected PDFs' with a specific verb and resource, and adds the purpose 'so Paperless can OCR them'. This clearly distinguishes it from siblings like rotate_documents or merge_documents, even without naming an alternative.

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?

It provides clear context: use this when you need to make password-protected PDFs processable by Paperless OCR. The caveat 'only use it against an instance you control' gives an important restriction, though it doesn't explicitly enumerate alternatives or when-not-to-use conditions.

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