列出微信聊天

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

Description adds context beyond annotations: it specifies the data source ('plaintext snapshot') and pagination behavior ('offset/limit'). Annotations already indicate read-only and idempotent, and description aligns with those. No contradictions.

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?

Single sentence with no filler. Front-loaded with the core action and resource, followed by key features. Every word is informative and earns its place.

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 output schema exists, the description does not need to explain return values. It covers source, filtering, and pagination. However, it omits any limitations (e.g., max results) or error conditions. Still, for a read-only list tool, it is largely complete.

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 description must compensate. It explains '关键词' (keyword) for query, and 'offset/limit 分页' for pagination, covering three of four parameters. The 'response_format' parameter is not mentioned, leaving a gap.

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?

Description clearly states '列出明文快照中的联系人和群聊' (list contacts and group chats in plaintext snapshot), specifying the resource (chats) and scope (snapshot-based). It distinguishes from sibling 'wechat_list_recent_chats' by emphasizing 'snapshot' rather than recent data.

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?

No explicit guidance on when to use this tool versus siblings like wechat_list_recent_chats. The description only lists capabilities without stating use cases or alternatives.

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