Create temporary or permanent QR codes with scene parameters for WeChat Official Accounts. Use scene_id or scene_str for tracking and expire_seconds to limit temporary code validity.
创建临时或永久参数二维码。
| Name | Required | Description | Default |
|---|---|---|---|
| scene_id | No | ||
| scene_str | No | ||
| action_name | Yes | ||
| expire_seconds | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate a mutating, non-idempotent operation. The description adds only the temporary vs. permanent functional distinction, but does not disclose side effects, return behavior, auth needs, or rate limits. It does not contradict the annotations, but it provides little behavioral transparency beyond them.
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 front-loaded sentence with no filler, which is concise. However, given four undocumented parameters and the need to explain the temporary vs. permanent distinction, this length is under-sized and leaves out necessary operational detail.
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 is insufficient for an agent to call the tool correctly: it does not explain how to fill the parameters, how to choose between scene_id and scene_str, what expire_seconds means, or what the output will be. The existing annotations and output schema soften the gap slightly, but the core decision logic 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 description coverage is 0%, so the description bears the full burden of explaining parameters. It does not mention action_name, scene_id, scene_str, or expire_seconds, nor how they interact. The phrase '临时或永久' only vaguely hints that expire_seconds might be related to the temporary/permanent mode.
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 uses a specific verb ('创建') and a specific resource ('参数二维码'), and clearly distinguishes two modes: temporary and permanent. It is unambiguous against sibling tools like create_menu, create_draft, or create_tag, which create entirely different resources.
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, nor does it explain the conditions for choosing a temporary QR code over a permanent one. No prerequisites, exclusions, or alternative tool names are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.