获取最近微信消息

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

Annotations already cover readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds the specific behavioral detail that messages are returned in reverse chronological order, which is useful but not extensive. It does not mention pagination, rate limits, or edge cases, but the annotations cover safety profiles.

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 wasted words. It efficiently conveys the core purpose and scope.

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 low complexity (3 optional params, no required) and existence of an output schema, the description is minimally adequate. However, it omits parameter details for limit and response_format, and lacks any usage context or examples. It meets the bare minimum but is not comprehensive.

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 must compensate. It only clarifies the 'chats' parameter by mentioning 'specified chats or all chats'. The 'limit' and 'response_format' parameters are not described at all, leaving their purpose unclear without external knowledge.

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 tool returns recent messages from specified chats or all chats in reverse chronological order. It uses a specific verb (返回) and resource (最近消息), and the scope is well-defined, distinguishing it from siblings like wechat_read_chat or wechat_search_messages.

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, such as wechat_search_messages for filtered queries or wechat_read_chat for a single chat's full history. No when-to-use or when-not-to-use conditions are mentioned.

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