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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavior: the tool 'opens nothing by itself' and returns instructions rather than executing anything, so no browser session is created as a side effect. It also discloses the API access constraint (Enterprise-only, email token), which explains why a browser-driven path is needed.

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 information is front-loaded, but the opening clause 'from ChatGPT, Claude or any AI agent' is filler, and the second sentence chains three separate ideas (non-execution, next-step tools, API availability) into one run-on. The Enterprise-API note is useful but appended awkwardly rather than structured separately.

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 definition covers what matters: what is returned (a step-by-step guide with screens, buttons, fields), that no action is performed, and which tool family completes the task. The main residual gap is that it does not say what the guide does if the client list is empty or the account lacks access, but that is minor.

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 the schema is an empty object, so there is no parameter meaning to convey. The description correctly mentions no arguments and instead spends its words on output shape and prerequisites, which is the right allocation for a no-arg tool.

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 verb and resource ('List clients in the user's own Everfit account') and then immediately clarifies the real nature of the tool: it returns step-by-step instructions rather than data, and does not open anything itself. This resolves the ambiguity created by the name 'list_clients', which would otherwise suggest direct data retrieval. It does not explicitly contrast itself with sibling read tools such as everfit_get_client_overview, which keeps it short of a 5.

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 gives clear operational guidance: use this to obtain the procedure, then execute it with the cotlet_browser_* tools in the user's Everfit Cloud Browser. That tells the agent both when the tool applies and what to do next. It stops short of explicit exclusions (e.g., when to prefer everfit_get_client_overview over this workflow), so it is clear context rather than full routing guidance.

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