decrypt_pdf

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that a correct password is required and that this is not a brute-force cracker, which materially shapes expectations of failure. However, it says nothing about whether the file is rewritten in place, how 'overwrite' behaves, or what happens on a wrong password.

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 short sentences, no filler, with the operation stated before the disqualifying caveat. Every clause 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?

No annotations, no output schema, and 4 undocumented parameters mean the description is the only source of behavior, yet it omits output destination and overwrite semantics — the details most likely to cause a wrong or destructive call. Inadequate for a 4-parameter mutating 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 description coverage is 0% across 4 parameters, so the description must compensate and largely does not. It conveys the semantics of 'password' (it must be the correct one) but leaves input_path, output_path, and especially the write-affecting 'overwrite' flag entirely unexplained.

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 ('Remove the password from a PDF') plus the precondition ('given its correct password'), so the agent knows exactly what operation this performs. The inverse relationship to the sibling encrypt_pdf is evident, though it is never named explicitly, which keeps this from a 5.

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?

'Given its correct password' defines the condition for use, and 'Not a cracker' explicitly defines when NOT to use it (unknown/forgotten passwords). It offers no alternative route for the password-unknown case, so it falls just short of full when/when-not/alternatives coverage.

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