pdf_add_watermark

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

The description adds behavioral context beyond annotations by specifying default positioning (centered, rotated diagonally) and page range application. Annotations are not contradicted. However, it does not detail side effects, performance, or file impact, so transparency is moderate.

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 extremely concise: two sentences with no wasted words. It front-loads the essential action and resource, then adds key default information. Ideal structure for quick comprehension.

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 8 parameters, 100% schema coverage, and existing annotations, the description sufficiently covers default behavior and page range handling. It does not explain the output or side effects, but the output path is self-explanatory. Overall, it is complete for a watermarking tool with good schema support.

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?

All 8 parameters are fully described in the input schema (100% coverage). The description adds context about defaults and page range behavior (e.g., 'Applies to all pages if no page range is specified'), but this largely reinforces existing schema info. Thus, the description adds marginal semantic 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 clearly states the action ('Add a text watermark') and resource ('PDF pages'), and includes default behavior (centered, rotated diagonally). It effectively communicates the tool's purpose, though it does not explicitly differentiate from siblings.

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?

The description provides minimal usage guidance, only mentioning that it applies to all pages if no page range is specified. There is no discussion of when to use this tool versus alternatives or exclusions, which is a gap for an 8-parameter tool.

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