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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower, and the description still adds the key behavioral fact: it "opens nothing by itself" and only returns instructions. That is exactly the side effect an agent needs to know about. The cryptic trailing fragment "Mindbody's official API: Yes." adds noise rather than transparency, and no return format detail is given.

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 message is front-loaded and short, which is good, but the sentence about ChatGPT/Claude/any AI agent is filler and the closing "Mindbody's official API: Yes." is an unexplained fragment whose meaning is unclear. Tightening to two sentences would lose nothing.

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 input schema fields and no output schema, the description carries the burden of explaining what comes back, and it does: a step-by-step procedure with screens, buttons, and fields. Combined with the hand-off to cotlet_browser_* tools, an agent can call this and know what to do next. The only gap is the undefined API-status remark.

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 there is nothing for the description to disambiguate and the baseline of 4 applies. The description does not need to explain argument semantics, and it correctly implies no inputs are required to obtain the guidance.

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 opening sentence says "Search clients in the user's own Mindbody account," which reads as a direct action, but the second sentence reveals the tool actually returns step-by-step instructions (screens, buttons, fields) rather than performing the search. The clarifying clause rescues it, but an agent skimming the first line could easily misclassify this as a data-retrieval tool alongside mindbody_get_client_visits or mindbody_get_class_roster.

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?

The description establishes a clear workflow: this tool produces the how-to, then the agent executes it with cotlet_browser_* tools in the user's Mindbody Cloud Browser. That is real routing guidance that separates it from both the direct data tools and the browser primitives. It stops short of an explicit when-not condition or a named alternative for retrieving client data programmatically.

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