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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, and the description adds genuinely new behavioral information: it 'opens nothing by itself' and its output is a step-by-step procedure rather than data. That is exactly the kind of side-effect disclosure annotations cannot convey. The trailing 'Mindbody's official API: Yes.' adds no usable behavior detail.

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 hand-off information is present but the sentence structure is tangled, combining the return-value description with a side-effect caveat in one clause chain. Filler such as 'from ChatGPT, Claude or any AI agent' and the opaque 'Mindbody's official API: Yes.' consume space without adding decision-relevant meaning.

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 output schema, the description carries the burden of explaining returns, and it does so only briefly ('screens, buttons, fields'). For a tool whose entire value is a procedure that drives subsequent browser calls, more detail on the shape of that output and the hand-off would help. It is adequate but thin for a guide-style 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 takes zero parameters and schema coverage is 100%, so the baseline is 4 and there is nothing for the description to compensate for. No parameter-level meaning is missing.

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?

Names a specific verb and resource ('List client contracts in ... Mindbody account'), then explicitly clarifies that it does not perform the action itself but returns step-by-step instructions and hands off to cotlet_browser_* tools. That hand-off distinguishes it from siblings like mindbody_terminate_contract. The phrasing is slightly self-undermining, since 'List' suggests a data-returning call while the text says it returns a procedure, but the intent is still recoverable.

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 next step ('then do it with the cotlet_browser_* tools in the user's Mindbody Cloud Browser'), which is useful sequencing guidance. However, it never states when to prefer this over other Mindbody contract or client tools, nor any prerequisite (e.g., being authenticated in the Cloud Browser) beyond the vague reference to the user's own account.

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