vrchat_events_discover

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

Annotations already declare readOnlyHint=true; description adds 'read-only' parenthetically but provides no further behavioral context (e.g., pagination, ordering, rate limits). Limited added 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?

Single concise sentence is front-loaded but too sparse given 16 parameters. Every word earns its place, but lacks structure for parameter details.

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 presence of an output schema, description is incomplete for a tool with 16 parameters including enums and pagination. Does not guide usage of filtering, pagination, or result format.

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%; description only mentions 'category/tag filters' (categories, tags). Fails to explain other 14 parameters (scope, fields, compact, pagination, etc.) leaving agent uninformed.

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?

Description clearly states the action 'Discover', the resource 'public calendar events', and optional filters. Distinguishes from sibling tools like vrchat_events_upcoming and vrchat_events_search by focusing on discovery with filters.

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?

Implies usage for read-only discovery with filters, but does not explicitly state when to use this tool versus alternatives. No exclusions or context for replacement.

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