vrchat_events_upcoming

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

The description accurately labels the tool as read-only, which aligns with the readOnlyHint annotation and adds no contradiction. It further specifies the default time window, providing behavioral context beyond the annotation. For a simple listing tool with output schema, this is sufficient transparency.

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, efficient sentence that conveys purpose, scope, and default behavior without extraneous words. It is front-loaded with the core action and provides additional details concisely.

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 8 parameters and no required parameters, the description is too sparse. It fails to explain how to use the parameters to navigate or filter events, leaving a significant gap for an agent. While the output schema compensates for return values, the input semantics are not addressed.

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 description does not explain any of the 8 input parameters despite 0% schema description coverage. Key parameters like 'from', 'fields', 'compact', 'windowHours' remain undocumented, leaving the agent without critical guidance on how to customize the query. The default window hint only indirectly relates to 'windowHours' but is insufficient.

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 verb 'List', the resource 'calendar events', and the scope 'in the upcoming window'. It also specifies default behavior (next 7 days) and marks the tool as read-only, effectively distinguishing it from sibling event tools like vrchat_events_discover and vrchat_events_search.

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?

The description mentions the default window of 7 days, giving a sense of when the tool is appropriate. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., vrchat_events_search for broader searches) and does not provide exclusion criteria or prerequisites.

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