render_markdown

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

With no annotations, the description carries full responsibility for behavioral disclosure. It clearly states the transformation but does not mention details such as whether raw HTML in Markdown is preserved/sanitized, how the title parameter affects output, or the exact return type. For a simple pure conversion this is acceptable but not rich.

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, front-loaded sentence perfectly captures the tool's purpose with no filler. Every word earns its place.

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 two-parameter conversion tool with fully documented schema, the description is largely complete. It would be stronger if it clarified the return value and sanitization behavior, but nothing essential is missing for an agent to understand the basic call.

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. The description adds little semantic value beyond restating the conversion; it does not clarify how title interacts with markdown or what kind of HTML document is produced.

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 uses a specific verb and resource: 'Render a Markdown string to an HTML document.' This unambiguously identifies the input and output format and distinguishes it from the unrelated sibling tools (count_pages, verify_delivery, ship).

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 usage context is implied: the tool is for converting Markdown to HTML. However, there is no explicit guidance about when to prefer this tool over alternatives or when not to use it, though none of the listed siblings are directly related.

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