Markdown to PDF

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

Annotations already indicate idempotentHint=true and no destructiveness; description adds value by disclosing the browser dependency, fallback to HTML, and relation to cc_md_to_html. No contradictions found.

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, with meaningful sections. It front-loads the main action and includes args list. Minor verbosity in the fallback line could be trimmed.

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 simplicity (3 params, no output schema, idempotent), the description covers the core behavior, browser requirement, and fallback. However, it could mention possible errors or output location clarity.

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% (all params described generically), but the description adds details like the optional title doc title and the browser dependency, which are useful but not essential. Score reduced because the description largely repeats parameter names without deeper semantics.

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 verb 'converts' and the resource 'Markdown to PDF', specifying the browser-based approach and distinguishing it from sibling cc_md_to_html by mentioning the same parser and fallback behavior.

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 indicates when to use this tool (for PDF conversion), mentions a prerequisite (Edge/Chrome), and a fallback (to HTML). However, it does not explicitly state when NOT to use it or compare with siblings like cc_convert_format.

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