Markdown table

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

Annotations already cover readOnly/idempotent/closed-world, but the description adds real behavior: pipes escaped as \|, line breaks as <br>, CSV delimiter detected from the first line, and that a >1,000,000-character result is always written to a file. That last point is worth flagging against readOnlyHint=true, since the 'output' option makes the tool write to disk, though the write is an optional side channel on an otherwise pure transformation rather than a contradiction of the tool's stated purpose.

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 core purpose is front-loaded and the density is justified for 8 parameters with several formats. The first sentence is a long run-on that packs formats and options together, and the trailing web-version URL adds little for an agent, but nothing is padding.

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 an 8-parameter, zero-required, no-output-schema tool, the description covers input modes, format detection, alignment, padding, escaping, and the file-output escape hatch, and it implicitly establishes that the reply contains the Markdown text. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying that text/path/rows are alternatives (one-of) and by stating the 'auto' detection order (Markdown, then JSON, then CSV/TSV) and the default alignment behavior. Most remaining parameter detail is already in the schema.

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+resource ('Make a GitHub-flavoured Markdown table') and enumerates every accepted input shape (CSV, TSV, JSON array of objects/arrays, existing Markdown, 'rows' array). Directionality is unambiguous, which cleanly separates it from the inverse sibling markdown_table_parse without needing to name it.

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 clear context for invoking the tool and even routes between input modes ('Give "text", a file "path" or "rows"', plus 'use this for big inputs' on path). It stops short of explicit when-not-to-use or naming an alternative tool, so it lands just below the top mark.

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