pdf_set_metadata

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. 'Set metadata' implies a write operation but does not state whether existing metadata is overwritten, whether the file is modified in place, or whether any permissions are required. This significant gap leaves the agent without crucial behavioral context.

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 clear sentence, making it concise. However, it is under-specified; the brevity undermines informativeness. It does not waste words, but it could include more useful detail without becoming verbose.

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 tool's moderate complexity (two parameters, one being a nested object) and lack of annotations or output schema details, the description is incomplete. It fails to explain metadata formatting, overwrite behavior, return values, or any constraints, leaving the agent with insufficient context for correct invocation.

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%, so the description must compensate for parameter semantics. It does not mention pdf_path or metadata, or explain how the metadata object should be structured. While pdf_path is self-explanatory and metadata can be inferred as a key-value map, the description adds no explicit value 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?

The description uses a specific verb ('Set') and resource ('metadata for a PDF'), clearly indicating the tool's function. It is distinct from sibling tools that add text, images, or annotations, though it does not explicitly differentiate itself or mention 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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or exclusions. The usage is only implied by the tool's name and one-sentence description, leaving the agent to guess context.

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