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 mentions the priority rule for QR code paths, which is useful context, but lacks critical behavioral details: it doesn't specify whether this operation modifies the original PDF or creates a new file, what permissions or prerequisites are needed, potential side effects, or error handling. For a tool that likely mutates PDFs, this is a significant gap in transparency.

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 concise with two sentences that front-load the core purpose and include a key behavioral detail (priority rule). There's no wasted verbiage, though it could be slightly more structured by explicitly separating purpose from usage guidelines.

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 (7 parameters, likely mutates PDFs) and lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., success status, file path), potential errors, or important behavioral aspects like file handling. For a tool with this level of functionality, more context is needed to be fully helpful to an agent.

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?

The schema description coverage is high at 86%, so the schema already documents most parameters well. The description adds minimal value beyond the schema: it reiterates that QR code must be an image file (PNG/JPG) and mentions the priority rule, but doesn't provide additional semantic context like how 'friendly text' is formatted or what 'scale ratio' means practically. This meets the baseline for high schema coverage.

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: 'Add QR code to PDF documents with friendly text below.' It specifies the resource (PDF documents) and the action (add QR code), though it doesn't explicitly differentiate from sibling tools like 'add_watermark' or 'process_pdf_post_conversion' which might have overlapping PDF modification functions.

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 some usage context by stating 'Priority: user provided path > environment variable QR_CODE_IMAGE,' which helps understand parameter precedence. However, it doesn't explicitly guide when to use this tool versus alternatives like 'add_watermark' for other PDF modifications or 'convert_document' for format changes, leaving usage decisions implied rather than clearly defined.

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