WeChat_create_draft

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

With no annotations provided, the description carries the full burden. It discloses input/output fields, content constraints (<2万字符, <1M), default behavior for digest, and the access_token requirement. However, it does not describe side effects like whether existing drafts are affected or specific error behavior beyond listing 'success, error' outputs.

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 well-structured with a purpose statement, metadata overview, and parameter explanations. It is front-loaded with the core action. Some redundancy exists (metadata list repeats parameter names), but the overall length is appropriate and every line adds value.

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 description covers all parameters and output fields, which is good for a complex tool. However, it fails to explain how the eight logical parameters relate to the single 'args' string in the schema, leaving a critical invocation ambiguity. It also omits usage guidance. These gaps affect completeness.

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 schema is minimal with only an 'args' string and 0% description coverage, so the description is the sole documentation for parameters. It explains all 8 parameters, including optional flags, constraints, and defaults, fully compensating for the schema's lack of detail.

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 explicitly states '创建微信公众号草稿' (Create WeChat Official Account draft), which is a specific verb+resource action. It clearly distinguishes from sibling tools like WeChat_del_draft, WeChat_publish_draft, and WeChat_del_material by focusing on creation. The detailed parameter list further clarifies the scope.

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 no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or recommended use cases. While the tool name and sibling names imply its role, the description itself lacks explicit usage direction.

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