remove_pdf_metadata

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

With no annotations, the description bears full burden. It warns about overwriting the source file if output_file is omitted, which is critical. But it doesn't disclose error behavior, permissions needed, or that this is a destructive operation beyond removal.

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?

Structured with Args/Returns sections, but the extra formatting is typical and clear. Could be slightly more concise, but no filler.

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 output schema exists, the description suffices by stating return type. It covers parameter roles and the overwrite-behavior. Missing details on error handling or prerequisites, but acceptable.

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 has 0% description coverage, so description adds essential meaning: explains mutual exclusivity, defaults for output_file and remove_all, and clarifies that fields_to_remove is a list of strings.

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?

Description states 'Remove specific metadata fields or all metadata from PDF' with a clear verb-object structure. This distinguishes it from sibling tools like set_pdf_metadata (which modifies) and get_pdf_metadata (which reads).

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?

Explains mutual exclusivity between fields_to_remove and remove_all, which guides usage. However, it does not mention when to prefer this tool over set_pdf_metadata or other alternatives.

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