wechat_history

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

No annotations provided, so description must disclose behavioral traits beyond basic purpose. Description only states it is a read operation, but does not mention whether it requires an active listener, whether messages are marked as read, or how media messages are handled. Minimal behavioral context.

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, 8 words, front-loaded with key action. No unnecessary words, but could be slightly expanded to add parameter guidance without becoming overly long.

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?

With 3 parameters, multiple siblings, and an output schema (likely complex), the description is too minimal. It does not explain what the output contains, how parameters affect results, or typical use cases. Incomplete for effective tool understanding.

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% (no descriptions in schema). Description does not clarify the meaning of 'limit' (e.g., max number of messages) or 'msg_type' (e.g., filter by message type). Only chat_name is implied by 'specific WeChat conversation'. Fails to compensate for missing schema descriptions.

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 'Read chat history from a specific WeChat conversation', specifying verb (read), resource (chat history), and context (specific conversation). It distinguishes from siblings like wechat_new_messages and wechat_search.

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?

Description implies usage for retrieving historical messages from a named chat, but provides no explicit guidance on when to use this tool versus alternatives like wechat_new_messages (recent) or wechat_unread (unread). No exclusions or prerequisites mentioned.

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