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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the non-obvious behavioral fact that this tool performs no action and only returns instructions, plus the rationale that FitBudd has no public API. It does not describe prerequisites such as an active Cloud Browser session or what happens if the user is not logged in.

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 distinction (returns steps, does not act) is buried in the second sentence behind branding boilerplate ("from ChatGPT, Claude or any AI agent"). The closing sentence is circular — "FitBudd's official API: FitBudd publishes no public API" — and the "gone" reference is noise that does not help an agent decide or act.

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 tool with no output schema, the description covers what is returned (screens, buttons, fields) and what to do next, which is the information an agent needs. Missing only preconditions for the follow-on browser workflow.

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 schema has zero parameters and 100% coverage, so the baseline is 4. Nothing about arguments needs explaining, and the description offers no parameter detail because none exists.

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 the resource and scope precisely ("clients in the user's own FitBudd account") and clarifies that the tool returns step-by-step instructions rather than the client list itself. That clarification resolves the tension with the name "list_clients," but an agent skimming the name could still expect data back; the corrective sentence arrives second, not first.

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 usage path: call this to get the steps, then execute them with the cotlet_browser_* tools in the user's FitBudd Cloud Browser, and it explicitly notes the tool "opens nothing by itself." It does not contrast itself with cotlet_app_guide or explain when the browser path is unnecessary, so no exclusions are stated.

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