Read Current WeChat Tab

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

The description implies a read-only operation with the verb 'Read,' but the annotation readOnlyHint=false states the tool is NOT read-only. This is a direct contradiction, and no further context is provided to clarify actual side effects.

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 one concise sentence that clearly states the default and optional behavior without unnecessary detail. It is front-loaded and easy to parse.

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 description omits clarification of what 'attachable' means and conflicts with the tool name ('current tab' vs. 'first attachable'). However, the schema covers parameters and an output schema exists, so the description is adequate but not thorough.

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%, with all nine parameters described in the input schema. The description only references tab_id, adding no new semantics beyond the schema's existing documentation.

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 uses the verb 'Read' with the resource 'WeChat tab' and clarifies the default behavior (first attachable) and the alternative (specific tab by tab_id). It clearly distinguishes this from sibling tools like 'wechat_read_article' (reads an article) and 'wechat_list_tabs' (lists tabs).

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 usage pattern: use no tab_id for the first attachable tab, or provide tab_id for a specific tab. However, it does not explicitly state when to choose this tool over siblings or mention that tab_id can be obtained from wechat_list_tabs.

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