vrchat_group_invite

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

Annotations already indicate a write operation (readOnlyHint false). Description adds useful behavioral detail about confirmOverrideBlock overriding blocks. However, it does not disclose rate limits, permission requirements, or side effects of inviting (e.g., notifications, group membership changes).

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?

Two tightly written sentences with no filler. Front-loaded with core purpose, then key details. Every sentence contributes value.

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?

Despite presence of an output schema (reducing need for return value description), the tool has 8 parameters and many sibling tools. Description fails to cover 3 parameters, lacks guidance on required vs optional parameters (despite stating 'requires groupId or shortCode'), and offers no comparison to other invite tools.

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?

With 0% schema description coverage, the description adds meaning for 5 of 8 parameters (user, users, groupId, shortCode, confirmOverrideBlock). It clarifies user identifier formats and the confirmOverrideBlock default. Missing explanations for retry, dryRun, and continueOnError.

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?

Clearly states 'invite one or many users to a group' and specifies acceptable user identifiers (usr_ ids or display names). However, it does not explicitly differentiate from sibling invite tools (e.g., vrchat_invite, vrchat_invite_user) which serve different contexts.

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?

Provides guidance on requiring groupId or shortCode and explains confirmOverrideBlock's default and override behavior. Missing when to use this tool over other invite tools or when not to use it (e.g., permissions, self-invite not mentioned). Parameters like retry, dryRun, continueOnError lack usage context.

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