yuque_get_group_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, yet it only states the operation. It doesn't disclose permissions required for a group, the shape or scope of the 'summary statistics', rate limits, or what the response contains. The external doc pointer (references/api/statistic_api.md) is a lead, not inline disclosure.

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?

Two terse sentences plus a reference pointer; the purpose is front-loaded and nothing is padded. The reference to an external markdown file is slightly awkward but not wasteful.

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?

With no output schema and no annotations, the description should convey what the statistics actually contain and the safety profile of the call. It says only 'summary statistics' and defers to an external file, leaving the agent without inline knowledge of return values or access requirements.

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?

Single parameter with 100% schema description coverage ('Group login or ID (required)'), so the schema already documents it fully. The description adds nothing beyond echoing the ':login' path segment, so the baseline of 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 summary statistics'), which is clearer than a bare name restatement. It distinguishes itself from siblings like get_member_statistics and get_book_statistics by scoping to the group level, though it never explicitly contrasts with them.

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 on when to use this tool versus the sibling statistics tools (get_member_statistics, get_book_statistics, get_doc_statistics) or when a group-level summary is preferred over get_user_groups. Usage is only implied by the name.

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