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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds real context beyond that: results are ordered newest-first, dates are returned in the event's own time zone, and a Cotlet API key with app access is required — all useful behavioral details.

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?

Reasonably short and front-loaded with the resource scope before the ordering/auth details. The opening 'Whova: Events you can manage as an organizer' slightly restates the title, but every remaining sentence (ordering, chaining, time zone, auth) carries information.

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 zero-required-parameter list tool with no output schema, the description covers scope, ordering, time-zone semantics, chaining, and auth needs. The only missing piece is explicit guidance on the status filter's behavioral effect, which is minor.

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% and the single status enum is fully documented in the schema, so the description does not need to explain it. The description adds no syntax or default details beyond what the schema already provides, so this lands at the baseline 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?

States the resource (events) and scope (events you can manage as an organizer), and clarifies it returns every event of the organizer account newest-first. The verb 'list/returns' is implied via the title rather than stated outright, but the purpose is unambiguous and distinct from siblings like whova_list_sessions or whova_list_speakers.

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?

Adds one genuinely useful usage hint: reuse event_id from each item in the other tools, which supports chaining. However, it gives no guidance on when to use this versus alternatives, nor when to choose status=upcoming vs past vs all, leaving the filtering decision to the schema.

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