yuque_list_group_members

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb 'List' implies a read-only operation, but the description does not mention pagination, ordering, authorization requirements, error behavior, or whether the response includes full member objects or only identifiers. This is a minimal behavioral hint at best.

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 a single, clear sentence that immediately communicates the tool's function with no redundant or unnecessary words. It is appropriately sized for a simple list operation.

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 simple 1-parameter list tool, the description covers the essential function and parameter adequately. However, since there is no output schema, the description should provide some indication of what the return value looks like (e.g., list of member usernames vs. full objects), which it does not. This is a clear gap, but the low complexity makes it minimally viable.

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?

The schema description for the only parameter 'login' is 'Group login name' with 100% coverage. The description's mention of 'group/team' aligns with the schema but adds no extra meaning, such as whether the login is a slug, ID, or display name, or how to obtain it. Baseline for high schema coverage is 3, and the description does not raise it.

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 clearly states the tool's function with a specific verb and resource: 'List all members of a group/team'. It is distinct from sibling tools like yuque_list_groups (which lists groups) and yuque_list_repos (which lists repositories), so the purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. It simply states the action without mentioning scenarios where it is or isn't appropriate, leaving the agent to infer usage from the tool name and siblings.

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