md-to-pdf-with-mermaid-mcp

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

No annotations are provided, so the description carries the full burden. It mentions that Mermaid diagrams are rendered, which adds useful behavioral context beyond basic conversion. However, it doesn't disclose other traits like error handling, performance limits, or file size constraints, leaving gaps for a mutation tool.

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 concise and well-structured in two sentences: the first states the core function, and the second adds a key feature (Mermaid diagram support). Every sentence adds value without redundancy.

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, no output schema, and 2 parameters, the description is minimal but covers the basic purpose and a notable feature. It's adequate for a simple conversion tool but lacks details on output behavior, error cases, or advanced usage, making it incomplete for full transparency.

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 schema already documents both parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema, such as format details or examples. Baseline 3 is appropriate when the schema handles the documentation.

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 function: converting Markdown files to PDF format. It specifies the input format (.md) and output format (.pdf), and mentions support for Mermaid diagrams. However, since there are no sibling tools, it doesn't need to differentiate from alternatives, so it doesn't reach the highest score.

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 implies usage when converting Markdown files with or without Mermaid diagrams to PDF, but it doesn't provide explicit guidance on when to use this tool versus alternatives or any prerequisites. With no sibling tools, this is adequate but lacks detailed context.

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