Unlock PDF

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), so the description's added value is the external-service disclosure ('uploaded to conv2pdf') and the cost model ('counts as one conversion'). These are real behavioral facts the agent needs and are not in the annotations; it does not, however, cover output file handling, which the schema carries instead.

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?

Three short sentences, front-loaded with the core action, then the boundary, then the operational cost. No padding and nothing important is buried.

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 3-parameter, single-purpose tool with full schema coverage and annotations covering the safety profile, the description supplies the two things structured fields cannot: the external upload and per-call quota cost. Return-value behavior is left implicit, but there is no output schema and output_path is documented in the schema.

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%, including non-obvious guidance that password can be omitted for print/copy-restricted files, so the baseline is 3. The description only reinforces the 'known password' condition and adds no syntax or format detail beyond the schema.

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?

States a specific verb and resource ('Removes the password and the restrictions of a PDF') and immediately bounds the scope ('whose password is known') and what it is not ('does not find a forgotten password'). An agent can separate this from protect_pdf and the rest of the conversion siblings without opening a schema.

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?

Gives a clear use condition (password is known) and an explicit exclusion (forgotten passwords are not recovered). It does not name an alternative tool for the excluded case, but the condition that selects this tool is unambiguous.

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