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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely new behavioral context: the default date window, the weekend-style multi-day windowing, and that results are sorted by start time. Return shape and pagination semantics are not described, but no output schema exists to cover that either.

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?

Three tight sentences with zero filler, front-loading the resource and scope, then defaults, then optional filters and sort order. Every sentence carries information an agent needs.

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 read-only, fully-schema-documented listing tool with no output schema, the description covers scope, defaults, filtering, windowing, and ordering. The remaining gap is what an event record actually contains and whether results are truncated by `limit` silently, which an agent might want to know.

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 a baseline of 3 applies. The description still adds value by enumerating the full category taxonomy (including 'other-fun-deals', which the schema only gestures at with 'e.g.') and by spelling out the date/days windowing intent that maps to two parameters.

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+resource: curated things-to-do/events listings scoped to a DoStuff metro. An agent immediately knows this is a content-retrieval tool, and it is clearly distinct from siblings like metros (which enumerates metros) or prediction-market tools. It does not explicitly name a sibling alternative, which keeps it at 4 rather than 5.

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?

Explains the default window (today) and how to widen it with `date`/`days` (e.g. a weekend), plus the optional category and free-only refinements. That gives an agent clear invocation context. It lacks explicit when-not-to-use or alternative-tool routing, so it falls short of 5.

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