yuque_get_member_statistics

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

No annotations are provided, so the description carries the full behavioral burden. The GET endpoint implies a read-only operation, but the description says nothing about permissions, pagination limits, default sort behavior, or what the response contains.

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?

Very short and front-loaded: purpose, endpoint, and a reference pointer. Nothing is padded, though the Chinese reference note ('详见 references/api/statistic_api.md') is cryptic to an agent that cannot resolve the path.

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 stateless read tool with a 100%-covered schema this is minimally viable, but with no output schema the description could profitably say what statistics are returned or how they are grouped. As written, an agent knows how to call it but not what it gets back.

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 100%, so the schema already documents all seven parameters (name, page, limit, login, range, sortField, sortOrder) including defaults and enum-like value lists. The description adds no parameter detail beyond this, so the baseline 3 applies.

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?

States a specific verb and resource ('Get group member statistics') and the underlying endpoint sharpens the scope to member-level stats. The 'member' qualifier implicitly separates it from the sibling yuque_get_group_statistics, though the differentiation is never stated outright.

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 versus yuque_get_group_statistics, yuque_get_group_users, or the other statistics tools. Usage must be inferred entirely from the tool name.

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