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 useful payload context — the result is a roster of clients with sign-in/late-cancel status — and pins the upstream API (GET /class/classvisits), but says nothing about pagination, volume limits, or auth requirements for a potentially large roster.

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 compact sentences, front-loaded with the resource and immediately followed by a clarifying gloss and the API mapping. Nothing is redundant and nothing is wasted.

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 a fair job of characterizing the return (roster plus sign-in/late-cancel status) and the filtering semantics via the schema's last_modified_date. It is close to complete for a two-parameter read tool, missing only pagination/bounding behavior.

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 both parameters (class_id, last_modified_date) are already fully documented with format examples and provenance. The description contributes no additional parameter meaning, which is the baseline 3 case when the schema does the work.

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 ('Get one class with its visits') and disambiguates the term by defining visits as 'the roster of clients booked into it, with sign-in / late-cancel status.' It effectively separates itself from the per-client sibling (mindbody_list_client_visits) by scoping to a single class, though it never names an alternative 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?

There is no when-to-use or when-not-to-use guidance and no alternatives are mentioned. The only prerequisite signal ('from mindbody_list_classes') lives in the schema, not the description, so an agent reading the description alone gets no routing help.

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