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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the underlying endpoint (TeamUp: GET /events) and the shape of returned data, which is useful context, but says nothing about pagination behavior, default page size, or how expand/fields affect the payload — details that matter for a 15-parameter list tool.

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 sentences, no filler, with the core purpose and return fields front-loaded. The second sentence is a dense enumeration of filter dimensions, which is slightly hard to scan but still earns its space.

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 15-parameter, zero-required read tool with no output schema, the description usefully previews the returned fields and the filter surface, and annotations cover safety. It stops short of explaining pagination defaults or expand/fields interplay, but that gap is modest given the thorough schema.

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 every parameter (ids, page, sort, expand, fields, status, venues, instructors, starts/ends bounds, occupancy_status, page_size) is already documented in the schema. The description merely restates the filter categories without adding format, default, or interaction semantics beyond what is structured.

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 (list) and resource (scheduled sessions — classes and appointments), and enumerates the returned fields (time, status, capacity, counts, instructors, venue). An agent can distinguish it from the sibling goteamup_get_event (single event) and goteamup_list_attendances without opening either schema.

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 second sentence lists the filterable dimensions (time window, instructor, venue, offering type, status, occupancy), which implies when the tool is useful, but it never states when to prefer it over goteamup_get_event or goteamup_list_attendances, nor mentions exclusions or prerequisites. Usage is implied rather than prescribed.

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