同步本地微信数据库快照

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

The description adds behavioral details beyond annotations: it explains the tool decrypts to a read-only snapshot, does not modify source files, and does not send messages. This aligns with destructiveHint=false and idempotentHint=true. No contradictions with annotations.

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 two sentences in Chinese, efficient but missing parameter details. It front-loads the core purpose, but the structure could be improved by adding parameter explanations in a clear format.

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 the tool's complexity (two optional parameters, no enums, output schema exists), the description only covers high-level purpose and safety. It fails to document input parameters, leaving the agent underinformed. Output schema exists but is not referenced, reducing 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 input schema has two parameters (key_file, output_dir) with 0% description coverage, and the tool description does not explain their meaning or format. Without any parameter guidance, an agent cannot correctly supply values.

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 action: decrypting a WeChat database with a 64-bit hex key into a local read-only snapshot. It specifies the resource (db_storage) and verb (decrypt/create snapshot), and distinguishes from siblings by focusing on local snapshot creation rather than reading or searching.

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 gives a recommendation (exit WeChat before execution) and states safety (no modifications, no messages), but does not explicitly state when to use this tool versus alternatives like wechat_read_chat or wechat_list_chats. The guidance is present but not comprehensive.

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