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

Annotations already cover the safety profile (readOnly, non-destructive), so the description's added value is the exclusion rule ('Cancelled classes are not returned'), the start-order sort, and the auth requirement (Cotlet API key with app access). That is meaningful context beyond the structured fields.

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 tight and front-loaded, with the scope first and handoff note last. The first two sentences overlap ('classes on the calendar for a date range' vs 'lists classes on the calendar between two dates'), costing a bit of efficiency.

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?

No output schema exists, so the description must describe returns – and it does (Class ID, coach, reserved/waitlisted counts, ordering). With only two simple params and annotations covering safety, the definition is nearly complete; explicit pagination or volume limits are the only missing element.

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% for both params, so the schema already documents 'from' and 'to' including the default. The description only restates 'between two dates' without adding format or edge-case guidance. Baseline 3 is appropriate.

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 (lists) and resource (classes) with scope (calendar, date range) and payload contents (coach, reservation counts). An agent can distinguish this from pushpress_get_class_roster or pushpress_list_members without opening a 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 date-range framing implies when to call it, and noting the Class ID is what 'other tools need' hints at follow-on workflows. However, there is no explicit when-to-use vs. alternatives guidance (e.g. roster vs. list) or stated preconditions beyond the API key.

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