vibo_list_events

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

Annotations provide readOnlyHint=true, so the description only needs to add non-safety behaviors. It adds the default behavior (upcoming vs past) and the optional search filter, which are behavioral nuances beyond the annotation. It does not mention pagination defaults, but those are already in the schema. No contradiction; adds useful context.

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?

Two sentences, front-loaded with the core purpose, then behavioral defaults, then optional filter. Zero waste, each sentence earns its place. The structure makes it scannable for an agent.

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?

For a list tool with four parameters, no output schema, and read-only annotation, the description covers the essential behavior, defaults, and filters. Pagination parameters are documented in the schema. The description does not explicitly describe the return format, but for a list operation this is often self-evident; combined with the rich schema, the tool is adequately specified.

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 100%, so the baseline is 3. The description adds extra meaning by clarifying that 'past' defaults to false (via 'Defaults to upcoming events') and that the search query is optional ('Optionally filter by a search query'). This goes beyond the schema's descriptions, which state defaults but not the optionality emphasis. Adds value without redundancy.

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 a specific verb (list) and resource (events), with an explicit scope: 'events you're part of (as host or guest)'. This differentiates it from siblings like vibo_get_event (single event) and vibo_list_event_users (users in an event). The default behavior and optional filters further refine the purpose.

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 explains when to use the tool and how to adjust it: 'Defaults to upcoming events; pass past:true for events that have already happened.' It also mentions an optional search filter. While it doesn't explicitly contrast with alternatives, the purpose statement makes it clear this is the general listing tool, and the exclusion of single-event retrieval is implied. Clear context without exclusions.

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