convert_markdown_to_wechat_html

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

With no annotations, the description carries the full burden. It discloses that the output HTML includes inline styles and is intended for copy/paste workflows, which are behavioral traits. It does not mention potential limitations or details about the conversion process, but for a pure conversion tool, it adequately describes the core behavior.

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, well-structured sentence that starts with the main verb 'Convert.' It wastes no words and immediately communicates the essential purpose and a key detail (inline styles).

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?

The tool has a simple parameter set, and the schema covers parameters. There is no output schema, but the description implies the output is HTML. It does not mention the return format in detail, but for this straightforward conversion tool, the description is sufficient given its simplicity.

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 100% coverage with descriptions for all three parameters (markdown, theme, title). The description itself adds no additional parameter information, so the baseline of 3 is appropriate. The schema already explains the parameters sufficiently.

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 that the tool converts Markdown to WeChat-friendly HTML, with a specific verb ('Convert') and resource ('Markdown to WeChat-friendly HTML'). It also mentions inline styles and publishing workflows. However, it does not explicitly differentiate from sibling tools like open_wechat_html_in_browser, though the distinct action implies differentiation.

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 provides a clear context: 'for copy/paste publishing workflows,' indicating when to use this tool. It does not mention alternatives or exclusions, but the use case is well implied. No explicit 'when not to use' is provided, but the stated purpose is clear enough.

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