save_to_wechat_draft

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

With no annotations, description clearly states the tool only saves as draft and never auto-publishes, which is critical for agent decisions. No mention of side effects or failure modes, but core behavior is well covered.

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?

Three sentences, no redundancy. Efficiently conveys purpose, constraint, and post-action step.

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?

Given no output schema, description adequately covers key behaviors for a 9-parameter tool. Could mention expected success feedback or error handling, but sufficient for core usage.

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% with all parameters described. The description adds value by linking html_content to transform_for_wechat output, providing workflow context beyond 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?

Explicitly states it saves processed content to WeChat draft box, distinguishing from siblings (estimate_originality, import_source, transform_for_wechat) which handle earlier stages. Emphasizes it only creates drafts, not auto-publish.

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?

Indicates when to use (after processing) and what not to expect (no auto-publish). Could be more explicit about prerequisites or when not to use, but context with siblings implies it's the final step.

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