vrchat_group_roles_manage

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the destructive nature is clear. The description adds that it performs assignments, removals, and CRUD operations on role definitions, which is consistent. However, it does not disclose permissions needed, side effects, or persistence behavior beyond what annotations hint.

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 sentence of 11 words, efficiently communicating the scope of the tool. No unnecessary text.

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 the tool's complexity (multiple operations on roles), the description lacks essential context: it doesn't specify required inputs, return values (despite an output schema being present), or how to target specific groups/roles. The empty input schema is a red flag that the description should clarify.

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 input schema has zero properties, which is highly suspect for a management tool. The description does not explain how the tool receives necessary inputs (e.g., group ID, role ID, member ID). Schema coverage is trivially 100%, but the lack of parameters is a critical gap that the description fails to address.

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 purpose: assigning/removing member roles and creating/updating/deleting role definitions. It uses specific verbs ('assign', 'remove', 'create', 'update', 'delete') and distinguishes it from read-only sibling tools like vrchat_group_roles and vrchat_group_members.

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 implies usage for role management but does not explicitly state when to use this tool versus alternatives like vrchat_group_roles (likely read-only). No exclusions or prerequisites are mentioned.

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