pdf_set_metadata

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

With no annotations, the description carries the full burden. It usefully discloses that only specified fields are changed and others remain untouched. However, it does not explain whether the original file is modified (outputPath suggests a new file is created), nor does it mention permissions, error conditions, or side effects.

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 sentences: the first states the action and lists fields concisely, and the second clarifies the partial update behavior. No wasted words; front-loaded with the core purpose.

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 tool with 8 parameters and no output schema or annotations, the description covers the essential purpose and behavioral nuance (partial update). It is mostly complete, though it could explicitly state that a new file is created at outputPath and that the original remains unchanged.

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 coverage is 100%, so baseline is 3. The description lists the metadata fields (title, author, etc.), which matches the schema but adds no new semantic information. The partial update behavior is more relevant to behavioral transparency than parameter semantics.

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 uses a specific verb 'Set or update' and clearly identifies the resource 'PDF document metadata fields', listing the fields involved. It distinguishes itself from sibling tools like pdf_info (which reads metadata) by its action of updating metadata.

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 is provided on when to use this tool versus alternatives such as pdf_info (which likely reads metadata) or other PDF modification tools. The description omits any context about prerequisites, typical use cases, or when not to use it.

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