wechat_pending_messages

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

With no annotations provided, the description carries the full burden. It discloses the destructive 'pop' behavior and auto-download side effects (media saved to ~/.wechatbot/pending-media/ and referenced by localPath). This goes beyond the schema, though it doesn't mention prerequisites like login or empty-buffer behavior.

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, front-loaded with the core action, and includes essential media-handling details. Every word adds value with no redundancy or fluff.

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 tool is simple (one parameter), but lacks an output schema and annotations. The description provides some return context (localPath for media), but does not explain the full message object structure, error cases, or whether authentication via wechat_login is required. This creates gaps for an agent invoking the tool.

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 schema has one parameter `limit` with default/min/max but no description. The description adds meaning by clarifying that it returns 'up to `limit`' messages, which directly explains the parameter's role. This fully compensates for the 0% schema description coverage.

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's function: 'Pop and return up to `limit` received WeChat messages that have been buffered since the last call.' This specific verb-resource pairing distinguishes it from sibling tools like send/login/status. Mentioning media auto-download further clarifies the scope.

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 implies a polling usage pattern by stating 'since the last call' and makes it obvious this is the retrieval tool among the siblings. However, it does not explicitly name alternatives or provide when-not-to-use conditions, so it falls short of a 5.

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