vrchat_event_create

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

The description merely says 'Create', which is a write operation, but this is already implied by readOnlyHint: false. No additional behavioral context is given (e.g., permissions required, side effects, or limitations).

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 extremely concise (one sentence), but it sacrifices necessary detail. While there is no wasted text, the brevity harms usability, making it merely 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 high parameter count (20) and zero schema descriptions, the description is critically incomplete. It lacks any context about required fields, defaults, or behavior, and does not mention the output schema, leaving the agent poorly informed.

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?

With 0% schema description coverage and 20 parameters, the description should compensate by explaining key parameters (e.g., tags, category, platforms). It does not, leaving the agent with no guidance on parameter usage.

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 'Create' and the resource 'group calendar event', which is specific. However, it does not distinguish this from sibling tools like vrchat_event_update or vrchat_group_events_list, leaving potential ambiguity.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives (e.g., updating events, listing events), which is a significant gap given the many event-related siblings.

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