Query IM message statistics

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

The readOnlyHint annotation already establishes that this is a safe read operation. The description adds useful scope by naming the statistics categories and common tab values, but it does not describe return behavior, pagination, or any limits beyond what the schema and annotations provide.

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 compact and front-loaded, immediately stating the tool's purpose and then giving the most common tab/childTab values. Every sentence adds useful selection information without repetition.

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?

For a 7-parameter statistics query with no output schema, the description covers the central required parameter and common childTab values but does not explain several optional parameters or what the result contains. It is minimally adequate but has clear gaps.

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 only 57%, so the description must carry more weight. It meaningfully explains tab and childTab with examples, but it leaves optional parameters such as app, productNumber, and yiDunBusinessId undocumented in both the description and schema.

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 a specific verb and resource: query IM statistics by tab/childTab, and lists the data categories it covers. It is clear what the tool does, though it does not explicitly distinguish itself from sibling stats tools such as yunxin_stats_users or yunxin_stats_app.

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 gives useful common values like tab=MESSAGE_COUNT and childTab=SINGLE_MESSAGE_COUNT, but it does not explain when to use this tool versus the other stats siblings or when to prefer different tabs. Usage is implied rather than fully guided.

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