vrchat_group_roles_manage

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description confirms destructive actions (delete roles, remove assignments). However, it adds no new behavioral context such as permission requirements, side effects, or limitations beyond the annotation.

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 that succinctly captures the full scope of actions. It is front-loaded, has no filler, and covers both role definition management and member role assignment.

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 (11 parameters, 5 actions), the description along with the rich schema and output schema provides enough context for an agent to understand what the tool handles and how parameters connect to actions. Minor gap: no guidance on when to choose specific actions, but this is partly addressed by the enum descriptions.

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?

Input schema coverage is 91%, so the schema carries the burden of parameter semantics. The description does not add parameter-level detail, but the schema descriptions are thorough, including distinctions like roleId versus groupRoleId and dependency notes.

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 specifies the resource (group roles) and multiple distinct verbs (assign, remove, create, update, delete). It differentiates from sibling tools like vrchat_group_roles by explicitly covering role definition CRUD and member role assignment/removal.

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, nor are any exclusions or prerequisites mentioned. The description only states what the tool does, not when it should be chosen.

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