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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false). The description adds real behavioral context beyond that: the exact status categories returned and the rule that a Waitlist member moves to Reserved when a spot opens, plus the auth prerequisite.

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?

Front-loaded with the core purpose, then return content, then edge-case behavior, then auth requirement. Every sentence carries information; the wording is a little unpolished but not padded.

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 one-parameter read-only tool with no output schema, the description covers purpose, returned statuses, and the auth requirement adequately. Return shape details are not strictly needed, though confirming output fields for each status group would add value.

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% and the single class_id parameter is documented in the schema as 'Class ID from list_classes'. The description adds no format or semantics beyond what the schema already provides, 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: members of one class grouped by status, returning the same statuses Core shows. This clearly separates it from a bare member listing, but it never names a sibling (e.g., pushpress_list_members) to disambiguate explicitly.

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?

Usage is implied: it returns the roster for a single class, and it notes the auth requirement (Cotlet API key with app access). There is no explicit when-to-use vs when-not guidance or named alternative operation.

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