vrchat_group_events_upcoming

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

The description explicitly says 'read-only', which is consistent with the readOnlyHint annotation. It adds the time window constraint, but no additional behavioral traits (e.g., data freshness, side effects, or limits) beyond what the annotation already declares.

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?

Single sentence with no filler. Every word adds meaning. Perfectly concise.

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 having 10 optional parameters and an output schema, the description is minimal. It does not explain the time window, group requirement (groupId/shortCode), pagination controls (maxItems, pageSize, maxPages), or compact/field selection. Incomplete for the tool's complexity.

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?

Schema coverage is 0%, so the description should compensate. It hints at a time window (implied by 'windowHours', 'from' parameters) but does not explain any of the 10 parameters. Most parameters lack any interpretive context, leaving the agent to guess.

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 it lists upcoming group events in a time window and is read-only. The verb 'list' and resource 'upcoming group events' are specific, and it distinguishes from sibling tools like vrchat_events_upcoming (non-group) and vrchat_group_events_list (possibly all events).

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 on when to use this tool versus alternatives. Siblings like vrchat_group_events_list and vrchat_events_upcoming exist but no exclusion criteria or usage context is provided.

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