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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this by explicitly saying it 'opens nothing by itself' and only returns instructions — valuable because the tool name otherwise reads as a destructive mutation. It could add more, such as whether it needs an authenticated browser session or what it returns when no contract exists.

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 behavior and the follow-up action are front-loaded in the first two sentences with no wasted preamble. The trailing 'from ChatGPT, Claude or any AI agent' and the dangling 'Mindbody's official API: Yes.' add marketing noise and ambiguity.

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 tool, the description covers what it returns (step-by-step screens, buttons, fields) and what it does not do. It leaves out session prerequisites and the fallback path when the contract is missing or not found.

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 no parameter semantics to explain beyond what the empty schema already conveys. Baseline 4 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?

The description states a specific resource (a Mindbody contract) and, crucially, clarifies that the tool does not terminate anything itself but returns a step-by-step procedure. That disambiguates it from both the mutation-flavored name and from the cotlet_browser_* execution tools it points to.

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 clear sequencing guidance: call this to get the screens/buttons/fields, then carry it out with cotlet_browser_* in the Cloud Browser. It does not state prerequisites (an open browser session, or that the target contract must first be identified via mindbody_list_client_contracts) or any when-not-to-use condition.

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