vrchat_invite_user_to_me

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

Discloses automatic resolution of current instance, adding value beyond annotations. However, misses side effects (e.g., notification to user, failure if not in an instance) and rate limits.

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 efficient sentences with no redundancy. Key information is front-loaded.

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?

Covers the core action and prerequisite but omits preconditions like being in an instance or user being a friend. Does not differentiate from similar sibling 'vrchat_invite_user'.

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 userId parameter is adequately described via context, but messageSlot (an optional integer) is not mentioned at all, leaving its purpose unclear despite schema coverage being 0%.

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 (invite) and the target (a user to your current instance). It distinguishes from siblings by highlighting automatic location resolution, which is unique among invite-like tools.

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 a clear prerequisite: if only a display name is known, use vrchat_friends_search first. Lacks explicit exclusions or alternative tools for different scenarios.

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