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

Annotations already declare readOnly, idempotent, and non-destructive, so the safety bar is low. The description adds real value beyond them: a hard 31-day window, the exclusion of names/emails/private notes (useful for knowing what the payload cannot answer), and the critical caveat that a single page is not a complete attendance total.

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 short sentences, each earning its place: scope and fields first, then data exclusions, then the interpretation caveat. Nothing is repeated from the title and there is no filler.

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?

With no output schema, the description does the work of listing returned fields and explicitly listing what is excluded, plus the pagination caveat. Remaining gap is the lack of any signal about how to detect further pages or what the response envelope looks like.

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 0%, so the description must carry parameter meaning. It covers the date window ('at most 31 days') and implies pagination ('one page'), but never explains page/count semantics, defaults, maximums, or the YYYY-MM-DD date format that the schema only enforces via regex.

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 ('Read one page of class visits'), the 31-day window constraint, and the fields returned (client IDs, pass and payment status). The resource is naturally distinct from the sibling reports (sales, active passes), but no sibling is named to explicitly route the agent.

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 through the 31-day cap and the warning that a page 'is not a complete attendance total', which steers the agent toward paging rather than aggregating. However, there is no explicit statement of when to choose this over fitssey_get_sales_report or fitssey_get_active_passes_report, and no guidance on iterating pages.

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