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

readOnlyHint=true already tells the agent this is a safe read; the description adds that the call is a GET and that results span both past and scheduled visits, which is genuine context. It does not, however, disclose pagination behavior or result ordering beyond what the schema already documents.

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 core scoping information front-loaded; the Mindbody endpoint reference is mildly redundant but earns its place as an implementation anchor. No wasted prose.

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, but the return concept (visits in a date range) is clear and the annotations cover the safety profile. With all 8 parameters fully documented in the schema, the description supplies enough for correct invocation.

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% – every one of the 8 parameters is documented in the schema, including date formats, page sizing, and the RSSID note. The description only echoes the date-range and unpaids_only concepts, 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 (list) and resource (client's visits), plus scope: past and scheduled class/appointment attendance within a date range. An agent can tell this is client-scoped rather than class-scoped, though it never names the sibling mindbody_get_class_visits to sharpen the contrast.

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 by 'a client's past and scheduled visits' and the optional unpaid filter, but there is no explicit when-to-use guidance or routing away from alternatives like mindbody_get_class_visits or mindbody_get_client_account_balances.

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