pdf_set_metadata

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

With no annotations, the description carries full burden but provides minimal behavioral context. It states the operation ('Set or update') but doesn't disclose whether this modifies the original file (vs. creating a new one), what happens if metadata fields are omitted, permission requirements, error conditions, or output format. The mention of 'output' parameter in schema hints at file creation, but this isn't explained in the description.

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, efficient sentence with zero wasted words. It front-loads the core purpose ('Set or update PDF metadata') and succinctly lists the fields without unnecessary elaboration, making it easy to parse quickly.

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 mutation tool with 7 parameters, no annotations, and no output schema, the description is incomplete. It lacks critical context such as whether the operation overwrites the original file, how partial updates work, what the output contains (e.g., success confirmation or error details), and any side effects or limitations. The high parameter count and mutation nature demand more disclosure than provided.

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 parameters are well-documented in the schema. The description adds marginal value by listing the metadata fields (title, author, subject, keywords, creator) that map to some parameters, but doesn't explain interactions (e.g., that 'file' and 'output' are required while others are optional for partial updates) or provide usage examples beyond what the schema already specifies.

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 verb ('Set or update') and resource ('PDF metadata') with specific fields listed (title, author, subject, keywords, creator). It distinguishes from siblings like pdf_info (which reads metadata) and pdf_create/merge/split (which create/transform PDFs), though it doesn't explicitly name alternatives.

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 guidance on when to use this tool versus alternatives is provided. While the description implies it's for modifying metadata, it doesn't specify prerequisites (e.g., needing an existing PDF file), exclusions (e.g., not for creating new PDFs), or direct comparisons to siblings like pdf_info for reading metadata.

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