typora_render_html

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

With no annotations provided, the description carries the full burden and does reveal useful behavior: the output is standalone, portable, and inlines base.css plus theme styling into the #write container. However, it does not disclose edge cases such as what happens when both content and input_path are supplied, whether Typora must be running, or whether the source file is modified, so transparency is partial.

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 entire description is one dense sentence with no filler. The core transformation is front-loaded, and the parenthetical detail about inlining base.css and theme styling earns its place by clarifying the output format.

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?

The description, combined with a fully documented schema, gives an agent enough to understand inputs and the general result for a straightforward render operation. The only real gaps are ambiguous combinations of optional parameters and lack of explicit return/error details, but these are minor given the tool's simplicity and complete schema coverage.

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 all four parameters. The description's phrasing 'Markdown content or an input Markdown file' maps to content and input_path but adds no per-parameter detail beyond what the schema provides. Baseline 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?

The description opens with a specific verb ('Render') and names both the input (Markdown content or file) and the output (standalone portable HTML). The mention of Typora's exact CSS themes and inlined base.css clearly distinguishes this from sibling tools like typora_get_theme_css or typora_open, which serve different purposes.

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 implied: use this when Markdown needs to be converted to styled HTML. However, the description does not explicitly state when not to use it or point to alternatives such as typora_create_document or typora_get_theme_css, leaving the agent to infer the right choice from the sibling list alone.

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