render_hwp_page

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

No annotations are provided, so the description carries the burden. It notes that omitting output_path returns the raw SVG string inline, but doesn't explicitly state side effects (likely read-only) or error conditions. The tool's name implies rendering, which is generally non-destructive.

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 two sentences, front-loaded with the main purpose and options. Every word earns its place, and it is easy to read.

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 simple tool with three parameters and no output schema, the description covers the key aspects. However, it does not mention error handling or the format of the returned SVG string, which could be considered a minor gap.

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 input schema has 0% description coverage, but the description compensates well. It explains that 'page' is 0-based with a default of 0, and that 'output_path' is optional with specific behavior when omitted.

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 renders a single page of an HWP/HWPX document as SVG. It distinguishes itself from sibling tools like 'render_hwp_all_pages' and 'render_hwp_html' by specifying 'single page' and 'SVG' output.

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 explains when to use inline output vs file output, and mentions it's useful for direct LLM consumption. However, it doesn't explicitly state when to use this tool versus alternatives like 'render_hwp_all_pages' or 'read_hwp_text'.

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