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

Beyond readOnlyHint/idempotentHint/destructiveHint=false, the description explicitly says the tool 'opens nothing by itself' and returns procedural guidance, which is important behavioral context. It does not cover auth or rate limits, but for a zero-param guide tool that is a minor gap.

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?

The core purpose is front-loaded, but the description includes marketing filler ('from ChatGPT, Claude or any AI agent') and the cryptic, unhelpful 'Mindbody's official API: Yes.' These phrases weaken otherwise useful workflow wording.

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, read-only how-to tool with no output schema, the description covers what it returns (screens, buttons, fields) and the required follow-up browser tools. It could be clearer about prerequisites, but it is sufficiently complete for this simple tool.

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 has no input parameters, so the schema carries no parameter semantics for the description to supplement. The description's lack of parameter discussion is appropriate.

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 names a specific verb and resource ('List classes') and scopes it to the user's own Mindbody account. It also clarifies that the tool returns step-by-step guidance rather than opening anything itself, though the phrasing 'List classes' versus returning instructions leaves some ambiguity.

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 a clear two-step workflow: use this tool to get Mindbody steps, then execute them with cotlet_browser_* in the user's Cloud Browser. It does not state when not to use it or name alternative Mindbody tools, so the guidance is strong but not exhaustive.

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