eb_org_events

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

The description adds the auth context that this operates 'as organizer', which is useful beyond the readOnlyHint annotation. It does not disclose pagination behavior or other operational details, but the annotation already covers the read-only nature.

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 concise sentence, front-loaded with the primary action and scope, with 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?

The description is minimal for a tool with four parameters and pagination. It does not explain the return shape or pagination continuation, but the schema provides parameter details. Given the simple list operation and read-only annotation, it is somewhat adequate but leaves gaps.

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 75%, with order_by lacking a description. The description mentions status filtering, which matches the status parameter, but adds no new meaning for org_id, order_by, or continuation. The schema already describes these parameters adequately.

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 an organization's events as organizer, with optional status filtering. This provides a specific verb and resource. It does not explicitly distinguish from the sibling tool eb_organizer_events, relying on the 'as organizer' phrase to imply the organizational scope.

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 gives no explicit guidance on when to use this tool versus alternatives like eb_organizer_events or eb_search_events. The intended use is implied by its function, but no exclusions or alternative recommendations are provided.

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