pdf_add_password

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

With no annotations, the description bears the full burden of behavioral disclosure, but only states the action without explaining side effects, output format, authentication requirements, or whether the operation is asynchronous. The presence of sibling tools like wait_job_completion and get_job_check suggests a job-based workflow, but the description remains silent on this.

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 sentence followed by a reference link. It is extremely concise, front-loaded with the core action, and contains no wasted words.

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 tool's complexity (17 parameters, no output schema, no annotations), the description is too minimal. It omits critical context such as the return value, the job-based workflow implied by sibling tools, and how to handle the generated output file.

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 100%, so all 17 parameters are already described in the schema. The tool description adds no additional parameter semantics beyond the general 'password protection' statement, so the baseline score of 3 is appropriate.

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's function: 'Add password protection to a PDF file.' It uses a specific verb and resource, and the verb 'Add' explicitly contrasts with the sibling tool 'pdf_remove_password'.

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?

No usage context is provided beyond the action itself. There is no mention of when to use this tool vs. alternatives, prerequisites, or when not to use it. The description does not differentiate from other PDF manipulation tools like pdf_merge or pdf_remove_password.

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