typora_export_pdf

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

With no annotations, the description carries the full burden. It usefully discloses that rendering is synchronous and uses a headless browser with 'valid file URIs,' which is real behavioral context. However, it omits overwrite behavior for the required output_path, error/failure modes, and any permission or environment requirements.

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?

A single dense sentence with the action and output format front-loaded. It is efficient, though the trailing clause about headless rendering and file URIs is a bit of a run-on.

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?

With no annotations and no output schema, the description should do more work. It covers the conversion and theme usage but leaves gaps on return behavior, overwrite semantics for the required output, and relationship to sibling render tools.

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 theme, content, input_path, and output_path. The description adds little beyond restating that content is Markdown text and input_path is a file source, so the baseline of 3 is appropriate.

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?

States a specific verb (Export) and resource (Markdown content/file to styled PDF), which is clear on its own. It does not explicitly contrast with the closest sibling typora_render_html, though the PDF-vs-HTML output difference is implied.

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?

Usage is only implied by the format conversion ('to a styled PDF'). There is no explicit when-to-use, no mention of when to choose this over typora_render_html, and no stated prerequisites or exclusions.

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