yuque_delete_group_user

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the destructive nature via 'Remove' and the safety guard confirm='DELETE', plus the endpoint. It does not state whether the removal is reversible, what permissions are required, or what the response contains — notable gaps for an unannotated delete tool.

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?

Three short fragments, front-loaded with the action and the critical confirm guard, followed by the endpoint and a reference pointer. Every element is useful; the mix of English and Chinese in the reference line is slightly uneven 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 annotations and no output schema, the description is the sole source of behavioral context. It covers the action, the safety guard, and the endpoint, but leaves permission requirements, reversibility, and return shape unspecified — adequate but incomplete for a destructive operation.

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 login, id, confirm, and raw in detail. The description only restates the confirm='DELETE' requirement, adding no syntax or format detail beyond the schema. 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+resource: 'Remove a member from a group', which clearly distinguishes it from siblings like yuque_get_group_users and yuque_update_group_user. It also names the underlying endpoint DELETE /groups/:login/users/:id, reinforcing the mutation semantics. No explicit sibling routing, but the purpose is unmistakable.

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?

Usage is implied by the clear 'remove a member' framing and the required confirm='DELETE' prerequisite, which is stated. However, there is no guidance on when to choose this over yuque_update_group_user or what prerequisites (admin role, group ownership) apply.

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