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

With readOnlyHint=true already declaring the safety profile, the description adds real value by disclosing the returned fields (capacity, attending and waitlist counts, instructors) that an agent cannot see without an output schema, plus the underlying API call ('TeamUp: GET /events'). It still omits pagination/sort defaults and any rate limits, so it is not exhaustive.

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 with the payload described first and filters second; no filler. The field enumeration is dense but each item is informative, and the API endpoint tag is a compact addition.

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 read-only list tool with no output schema, the description supplies a useful summary of the returned shape and the filter surface, which is the main gap the schema cannot fill. Minor omissions (pagination defaults, sort direction semantics) already live in the schema, so coverage is adequate.

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 all 15 parameters (ids, page, sort, expand, fields, status, venues, time bounds, instructors, offering_types, occupancy_status) are already documented in the schema. The description restates the filter dimensions at a high level without adding format, syntax, or default-value detail beyond the schema.

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?

Names a specific verb and resource ('List scheduled sessions — classes and appointments') and enumerates the payload it returns (times, status, capacity, counts, instructors, venue, offering type). An agent can distinguish it from goteamup_get_event 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 filter dimensions ('time window, instructor, venue, offering type, status or occupancy'), which implies the tool's use cases but does not state when to prefer it over alternatives such as goteamup_get_event or goteamup_list_attendances, nor any exclusions or prerequisites.

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