yuque_add_group_user

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

With no annotations, the description carries full burden for behavioral disclosure. It implies a mutation (add/update) but does not mention permissions, idempotency, side effects, or behavior on existing memberships. No information about response or errors is given.

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 concise sentence with no filler or redundant information. It is front-loaded with the verb and resource. However, its brevity comes at the cost of omitting necessary detail, which is penalized in other dimensions.

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?

Given no output schema, no annotations, and zero parameter documentation, the description is incomplete. It does not explain role semantics, identifier formats, or behavioral nuances. The tool is simple, but the context is too sparse for an agent to invoke it reliably.

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 0%, and the description does not explain any parameter. The 'role' parameter is constrained to 0 or 1, but no labels or meanings are provided. 'group' and 'user' are not clarified (e.g., identifier type). The description adds no value beyond parameter names.

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 action ('Add or update') and the resource ('a user membership in a Yuque group'), which distinguishes it from the sibling tool 'yuque_remove_group_user'. However, it does not explicitly mention the 'role' parameter or the fact that it can serve both creation and update, slightly blurring the purpose.

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 is provided on when to use this tool versus alternatives like 'yuque_remove_group_user' or 'yuque_list_group_users'. The description implies the operation but does not state preconditions, common scenarios, or exclusions.

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