eb_venue_events

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

The description only restates the tool's name and adds no behavioral details beyond the readOnlyHint annotation. It does not mention pagination via the continuation token, default status filter of 'all', or that results are limited to a single venue. The annotation already covers safety, so the description contributes no additional 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?

The description is a single succinct sentence with no redundant wording. It is appropriately minimal for a simple list operation and is front-loaded with the key action and resource.

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?

The description is overly sparse for a tool with 3 parameters, a pagination continuation token, and a status filter with 7 values. There is no output schema, so the description should at least mention that results are paginated or that the status filter defaults to 'all', but it does not.

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?

All three parameters are fully described in the input schema with clear descriptions and an enum for status, achieving 100% coverage. The description itself adds no parameter-level meaning beyond what the schema provides, matching the baseline of 3.

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 events for a venue, using a specific verb and resource. It does not explicitly distinguish from sibling tools like eb_org_events or eb_series_events, but the venue scoping is implicit in the tool name and description.

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 is provided on when to use this tool versus alternatives, nor are any prerequisites or use cases described beyond the basic listing function. The description only states what it does, not when to choose it.

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