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

The description adds real context beyond the annotations by stating it 'opens nothing by itself' (consistent with readOnlyHint=true) and that it returns procedural guidance, not data. But the 'official API: Yes' fragment muddies the picture by suggesting an API call, which conflicts with the browser-automation workflow it just described, and nothing is said about the guide's size or format.

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?

Three compact sentences that front-load the primary action and follow with the key behavioral caveat. The final 'Mindbody's official API: Yes' is an unanchored fragment that reads like a metadata tag and slightly dilutes the otherwise clean structure.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and it does: a step-by-step guide of screens, buttons and fields, plus the follow-up tool family. Only the ambiguous API note keeps it from being fully complete.

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 per-parameter meaning to convey and the schema is complete by construction. Baseline 4 applies; the description does not need to explain arguments.

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 name says 'Get client visits' but the description clarifies the actual behavior: it returns a step-by-step guide of screens, buttons and fields rather than the visit data itself, and points to cotlet_browser_* for execution. That specificity distinguishes it from data-returning siblings, though the tension between the name and the real behavior forces the agent to read carefully.

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 tells the agent the workflow order: get the guide here, then act with cotlet_browser_* tools in the Mindbody Cloud Browser. However, it never states when NOT to use it, gives no alternatives among the many mindbody_* siblings, and the trailing 'Mindbody's official API: Yes' leaves unclear whether an API path is an alternative or a claim about this tool.

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