weixin_poll

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 key behaviors: persistent cursor, prevention of re-delivery, and returning new messages since last poll. However, it lacks details on side effects, error handling, or what happens when no new messages are available, leaving some gaps.

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 three sentences long, each conveying essential information: the action, the cursor mechanism, and the output. It is front-loaded with the primary purpose and contains no redundant or filler text.

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 with one parameter and no output schema, so the description provides adequate context for its core function. It explains the cursor persistence and return behavior, but could be slightly more explicit about output format or edge cases, though these are minor for a polling 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?

Schema coverage is 100% and the single parameter reset_cursor has a clear description, so the tool description doesn't need to add much. The tool description's mention of a persistent cursor indirectly relates to the parameter but doesn't provide additional meaning beyond what the schema already offers.

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: polling for new WeChat messages. It uses a specific verb ('Poll') and resource ('WeChat messages') and differentiates from sibling tools like weixin_send or weixin_download by focusing on the retrieval of 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 implies its usage through the persistent cursor mechanism, making it clear this is for repeated polling to fetch only new messages. It doesn't explicitly name alternatives or exclusions, but the purpose is clear enough for an agent to choose it over sending or downloading tools.

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