vrchat_group_event_next

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

The description repeats the 'read-only' hint already present in annotations but adds no further behavioral context such as idempotency, rate limits, or authentication requirements. With annotations present, the bar is lower, yet the description fails to provide additional value.

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 front-loads the core purpose. However, it is overly terse, sacrificing necessary detail about parameters and context, making it minimally adequate.

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 has five parameters, no required ones, and an output schema, the description explains the tool's purpose but lacks details on how to use parameters (e.g., groupId vs shortCode) or what return values look like. It is insufficient for an agent to invoke the tool correctly without additional inference.

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 description coverage is 0%, meaning the input schema provides no descriptions. The tool description does not mention any of the five parameters (fields, compact, groupId, shortCode, maxArrayLength), leaving their semantics entirely unexplained. This is a critical gap.

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 verb 'Get', the resource 'next upcoming calendar event', and the scope 'for a group'. It distinguishes from sibling tools like vrchat_group_events_list and vrchat_group_events_upcoming by indicating singularity ('next'), but does not explicitly contrast with vrchat_group_event_get which might also fetch a single event.

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_group_events_list or vrchat_group_events_upcoming. There is no mention of prerequisites, context, or when not to use it.

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