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 tool's workflow dependencies, mandatory sequencing, and three core behaviors (move, add features, clean up). However, it doesn't mention potential side effects like file overwriting, permission requirements, or error handling for missing environment variables.

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 appropriately sized and front-loaded with the most critical information (workflow dependency). However, the emoji usage and formatting (🔧, ⚠️) add visual noise without semantic value, and the numbered feature list could be more concise. Every sentence earns its place by conveying essential workflow information.

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 complexity (14 parameters, no annotations, no output schema), the description provides good contextual completeness by explaining the mandatory workflow sequence and core operations. However, it doesn't describe the return value or error conditions, which would be helpful given the absence of an output schema and annotations.

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 the baseline is 3. The description doesn't add meaningful parameter semantics beyond what's already documented in the schema - it mentions watermarks and QR codes generally but provides no additional details about parameter interactions, defaults, or environment variable precedence that aren't already in the schema descriptions.

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 tool's purpose as a 'necessary follow-up step' that performs three specific functions: moving PDFs, adding watermarks/QR codes, and cleaning temporary files. It explicitly distinguishes this from sibling tools by mentioning it's specifically for post-processing PDFs generated by playwright-mcp, unlike general conversion or watermarking tools in the sibling list.

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 explicit usage guidance: it must be called 'immediately' after playwright-mcp's browser_pdf_save command, creating a clear workflow dependency. It also distinguishes when to use this tool versus alternatives by positioning it as a required follow-up to a specific playwright-mcp command, not as a standalone watermarking or QR code tool.

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