wechat_stats

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

The description only says 'Get statistics', implying a read operation, but does not disclose behavioral traits like whether it aggregates data, respects time ranges, or has any limitations. With no annotations, the description should provide more behavioral details, which it fails to do.

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 short sentence, which is concise but under-specified. For a tool with three parameters and no annotations, more detail is needed. It sacrifices completeness for brevity.

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 three parameters, zero schema coverage, and no annotations, the description is severely incomplete. It does not explain what statistics are returned, time range behavior, or prerequisites. It is insufficient for an agent to use correctly.

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 input schema has 0% description coverage, and the description adds no information about the parameters. It does not explain the purpose of start_time, end_time, or chat_name, or their expected formats. The agent gets no help beyond parameter names.

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 states 'Get statistics for a WeChat chat', which is a clear verb+resource. However, it is vague about what kind of statistics (e.g., message counts, frequency) and does not differentiate from siblings like wechat_history or wechat_members, which also provide chat-related data.

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?

No guidance is provided on when to use this tool versus alternatives such as wechat_history or wechat_members. The description lacks any context about appropriate scenarios or exclusions, leaving the agent without decision support.

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