Query app function usage statistics

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

readOnlyHint=true already tells the agent this is a safe read. The description adds that the call also returns IM security-check status, which is useful beyond the annotations. However, it doesn't describe what the statistics contain, time ranges, or response shape.

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?

A single compact sentence that is front-loaded with the primary purpose and adds the secondary security-check scope. No filler, though it is arguably too terse given the gaps it leaves.

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 2-parameter stats tool with no output schema and an undocumented app parameter, the definition should clarify the app identifier and what the statistics represent. The annotations cover safety, but the description does not fill the remaining informational 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?

Only 50% schema coverage: includeYidun is documented in the schema, but the app parameter has no description in either the schema or the description. The description's mention of '应用功能' hints at the app parameter but adds no format, type, or meaning beyond the field name, failing to compensate for the coverage gap.

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 names a specific verb (查询/query) and two concrete resources: application feature usage and IM security-check (安全通) detection status. This is clear enough to distinguish it from the config or auth siblings, though it doesn't explicitly contrast with close statistics siblings like yunxin_stats_im or yunxin_stats_users.

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?

There is no guidance on when to use this tool versus yunxin_stats_im or yunxin_stats_users, which cover adjacent statistics. The usage is only implied by the resource name, with no exclusions, prerequisites, or alternative routing.

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