vrcx_gamelog_world_visits_recent

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

The description explicitly says 'read-only,' which aligns with the annotation. It adds context that the data comes from the local VRCX gamelog, but does not disclose other behavioral traits like what happens if the gamelog is unavailable or the effect of parameters.

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 two sentences long, front-loaded with the core purpose, and every sentence is necessary. No wasted words.

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's simplicity, the description covers the essential functionality and uses. It has an output schema so return values need not be described. However, missing parameter details slightly reduces completeness.

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 input schema has two parameters (limit and daysBack) with 0% description coverage, and the description does not mention either parameter or explain their semantics. The description fails to add value beyond the schema.

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 tool lists recent world visits from the VRCX gamelog, specifying the verb (List) and resource (world visits) and indicating it is read-only. It distinguishes from sibling tools like 'vrcx_instances_recent' by explicitly mentioning the gamelog source.

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 says it reflects local activity history, which implies it’s for checking your own recent visits. However, it does not explicitly say when to use this vs. alternatives or provide any exclusions.

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