Get upcoming VR / AR / XR events

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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds that events are from VR.org's events calendar and sorted soonest first. No contradictions, and it adds useful behavioral context beyond annotations.

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 consists of two concise sentences. The first states the main purpose, the second gives a usage hint for the include_past parameter. No wasted words, well-structured.

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 no output schema, the description provides the source (VR.org), ordering (soonest first), and parameter hint (include_past). For a simple two-parameter list tool, this is fairly complete, though could mention return fields.

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%, so both parameters (limit, include_past) are documented in the schema. The description only mentions include_past explicitly, not adding significant meaning beyond the schema. Baseline 3 is appropriate.

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 returns upcoming VR/AR/XR industry events from VR.org's calendar, sorted soonest first, with examples (conferences, expos, launches). This is specific and distinct from sibling tools like compare_vr_headsets or get_top_vr_apps.

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 provides clear context: events are 'upcoming' and 'soonest first', and explicitly mentions the include_past parameter for including past events. It does not explicitly state when not to use it, but the purpose is clear enough.

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