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

Annotations already cover read-only, idempotent, non-destructive, and closed-world, so the safety profile is settled. The description adds genuinely new behavioral facts: the tool performs no browsing itself, the output is procedural instructions in terms of screens/buttons/fields, and execution is delegated to the browser tool family. It does not contradict the annotations.

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?

It is short and the most important fact (returns instructions, not data) is stated early, but the opening flourish about ChatGPT/Claude/any AI agent is filler and the final fragment 'Mindbody's official API: Yes.' is cryptic and unexplained, so not every sentence earns its place.

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 zero-parameter, no-output-schema guide tool this covers the essentials: what it returns and what to do next. However, with no inputs at all, an agent is left unsure how the requested class/roster context is supplied and whether account context is implicit, which matters before calling it.

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?

The tool takes zero parameters, so the baseline is 4. The description appropriately adds no parameter detail, though it also never explains how the target class is identified given there are no inputs — a small missed opportunity rather than a schema gap.

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?

The description discloses the tool's real behavior: it returns a step-by-step walkthrough (screens, buttons, fields) rather than roster data, and 'opens nothing by itself'. That distinguishes it from the mindbody_* data tools and the cotlet_browser_* action tools. The framing sentence ('Get class roster ... from ChatGPT, Claude or any AI agent') is boilerplate that briefly implies data retrieval, creating minor tension with the name, but the next sentence corrects it.

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?

It gives explicit sequencing: call this first to obtain the procedure, then execute it with the cotlet_browser_* tools in the Mindbody Cloud Browser. What is missing is any when-not guidance or a named alternative (e.g., for reading visit history use mindbody_get_client_visits), and the trailing 'Mindbody's official API: Yes' is too terse to be actionable guidance.

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