vrchat_system_time

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

Description repeats the readOnlyHint annotation, which is already provided. It adds no further behavioral details (e.g., return format, rate limits, authentication requirements). Consistent with annotations, so no contradiction.

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, no wasted words. Front-loaded with key info. Every word earns its place.

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 5 optional parameters and output schema, description is extremely minimal. It doesn't explain the time format, timezone, or why paging/fields are needed. Output schema may help, but description fails to provide sufficient context for effective tool usage.

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 100%, but description adds no value for parameters. The parameters (paging, fields, compact, includeMeta, maxArrayLength) are present but not explained, which is confusing for a time-fetching tool. Schema alone doesn't clarify their relevance.

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 verb 'Get' and resource 'current system time'. Name reinforces purpose. However, it doesn't explicitly differentiate from sibling tools like vrchat_auth_status or vrchat_status_get, which might also provide time-related info.

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 vs alternatives. The description doesn't specify context, prerequisites, or exclusions. An agent would need to infer usage from name alone.

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