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

Annotations only declare that this is a non-destructive, non-open-world operation, so the description carries the useful behavioral load: the output is self-contained with embedded CSS, the download URL expires in 10 minutes, and the upload id is single-use. What is missing is failure behavior (invalid markdown, expired upload id) and any content or size limits beyond 'large files'.

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?

Two sentences, both front-loaded with the highest-value facts: what is produced and what comes back first, then the escape hatch for large inputs. No filler and no repetition of the title.

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 output schema, the description usefully explains the return value (a 10-minute download URL) and the large-file path, which is enough for an agent to call it correctly. The one remaining gap is that the tool has zero required parameters and the description never states that at least one of markdown or markdown_upload_id must be supplied.

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 baseline is 3, but the description adds the operational workflow behind markdown_upload_id (POST to a stated URL, then pass the returned id) and reinforces the either/or relationship between markdown and markdown_upload_id. It stops short of restating the filename default, which the schema already handles.

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 states a specific verb and resource ('Converts markdown') and goes further to specify the output shape: a standalone styled HTML document with embedded CSS plus a time-limited download URL. Sibling differentiation is implicit but unambiguous, since convert_to_docx and convert_to_pdf target other formats and preview_markdown produces a preview rather than a downloadable document.

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?

It gives actionable routing for one real branch: large inputs should go through the upload endpoint and pass back the id, which is exactly the decision an agent would otherwise get wrong. It does not say when to prefer a sibling converter (PDF/DOCX) or when preview_markdown is the better choice for a quick look, so the guidance is clear but not complete.

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