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 the endpoint (GET /events) and the downstream-id hint, but says nothing about pagination behavior, ordering, or result limits beyond what the schema documents. Adding modestly on top of annotations merits a 3.

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 tight sentences plus an endpoint stamp. The returned-field list is front-loaded, the usage hint and filter hint follow, and no sentence is filler.

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?

With no output schema, enumerating the returned fields is genuinely valuable and mostly covers the gap; annotations cover the safety profile. Paging semantics (next_offset, ordering) live only in the schema, so one small piece of context is left to the structured fields rather than the description.

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% and every parameter (limit, offset, status, category) is already documented in the schema. The description only restates the status/category filtering, adding no syntax, defaults, or format detail beyond the structured fields, so the baseline 3 applies.

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 a specific verb and resource ('List the events in the Eventzilla account') and enumerates exactly which fields come back (id, title, dates, venue, status, tickets sold, categories, public URL). That scope cleanly separates it from sibling readers like eventzilla_get_event or eventzilla_list_event_attendees.

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?

Gives real context: call it to obtain the id/dateid that other tools need, and to filter by status and category (with a pointer to eventzilla_list_categories for valid category names). It stops short of explicit when-not guidance or naming an alternative for single-event lookups, so it is clear context rather than full routing.

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