vrchat_invite_user

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

The annotation readOnlyHint=false already signals a mutation, and the verb 'invite' aligns with that. No additional behavioral context is provided, such as whether the invitation requires friendship, is reversible, or triggers a notification.

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 that avoids redundancy. It is appropriately short for a simple statement, though it omits useful context.

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?

The tool has 5 parameters, an output schema, and several sibling invite tools, yet the description only provides a bare statement of function. It does not explain how to construct an invitation, what prerequisites exist, or how it differs from other invite tools, leaving significant gaps for the agent.

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 schema includes descriptions for worldId, location, and instanceId, but the tool description adds no parameter semantics. The missing descriptions for userId and messageSlot are not compensated, leaving the agent to infer from names alone.

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 states the action ('invite') and the target ('a user to an instance'), making the core function clear. However, it does not distinguish this from sibling tools like vrchat_invite_user_to_me or vrchat_group_invite.

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 such as vrchat_invite_user_to_me or how to specify the instance (via worldId+instanceId versus location). The schema provides some parameter hints, but the description itself offers no usage direction.

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