doc-ops-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes the priority system for watermark sources (text > image > environment variable > default), which is crucial behavioral context. However, it doesn't mention whether this operation modifies the original PDF or creates a new file, potential file size impacts, or error conditions.

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 perfectly front-loaded with the core purpose, followed by supporting details about watermark types and priority system. Every sentence earns its place by providing essential information without redundancy or fluff.

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 no annotations and no output schema, the description does well by explaining the core functionality and parameter interactions. However, it doesn't describe what the tool returns (e.g., path to watermarked PDF, success/failure status) or potential side effects, leaving some gaps in completeness.

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?

With 83% schema description coverage, the baseline is 3. The description adds significant value by explaining the priority hierarchy among watermarkText, watermarkImage, and fallback options, which clarifies the interaction between parameters beyond what the individual parameter descriptions provide in 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 specific action ('add watermarks') and resource ('PDF documents'), and distinguishes this tool from siblings by specifying its unique watermarking functionality. Unlike sibling tools focused on conversion, reading, writing, or QR codes, this tool is explicitly for watermarking PDFs.

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 clear context about when to use this tool (for adding watermarks to PDFs) and implicitly distinguishes it from siblings that handle different document operations. However, it lacks explicit guidance on when NOT to use it or named alternatives for similar tasks.

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