get_group_file_system_info

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. It does disclose what data is returned (total space, used space, file-count limit), which is useful since there is no output schema, but it says nothing about permissions, failure modes, or rate limits. For a simple read-only getter this is acceptable but not rich.

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 core purpose sentence is short and front-loaded, which is good. However, the appended docstring fragment ':param group_id: 群号' is redundant noise that duplicates the schema and slightly muddies an otherwise clean one-liner.

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 single-parameter, read-only getter with no output schema or annotations, the description is adequate: it names the resource and lists the kinds of values returned, partially compensating for the missing output schema. Missing guidance on prerequisites and sibling alternatives keeps it from a 5.

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% for the single group_id parameter, so the schema already documents it fully. The trailing ':param group_id: 群号' merely restates the schema text and adds no syntax, format, or constraint detail. Baseline 3 applies when the schema does the heavy lifting.

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+resource: retrieving QQ group file-system space usage (total space, used space, file-count limit). This is clearly distinct from sibling file tools like get_group_root_files or get_group_files_by_folder, which enumerate files rather than report quota. It lacks an explicit contrast to those siblings, so it falls just short of a 5.

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 call this versus the many sibling file/quota tools, nor any prerequisite or context such as needing the bot to be in the group. Usage is only implied by the name and resource. No when/when-not conditions are given.

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