Render Markdown

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the output includes HTML, front matter, and tags, and that it handles arbitrary Markdown. It also mentions the engine's capabilities. It does not describe error handling or side effects, but for a pure rendering tool this is adequate. No contradictions exist.

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 a single sentence with a parenthetical listing features, and it front-loads the primary action. Every word adds value—no filler, no repetition. It is appropriately sized for the tool's simplicity.

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 one-parameter tool with no output schema, the description is nearly complete. It states the input, the operation, and the return contents (HTML, front matter, tags). It does not mention potential limitations like size limits or error behavior, but given the tool's simplicity and the distinct nature of siblings, nothing essential 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 0%, so the description must compensate. It names the single parameter implicitly ('arbitrary Markdown') and makes it clear that the 'markdown' field is the input to render. This adds meaning beyond the schema's bare 'string' type, fully clarifying what the parameter represents.

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 verb 'Render' and the resource 'arbitrary Markdown to HTML'. It names the engine and specific features (GitHub alerts, KaTeX, tags, task lists), and distinguishes itself from sibling tools which all operate on notes/connections rather than rendering. An agent can immediately tell this is a conversion utility, not a CRUD operation.

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?

No explicit when-to-use or alternatives are mentioned. The description implies it should be used when you need to convert Markdown to HTML, but it doesn't state exclusions or situations where another tool would be preferred. Since all siblings are note/connection operations, the purpose itself provides clear differentiation, but the guidance is not explicitly stated.

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