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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so safety is covered; the description adds genuinely new context by clarifying the tool performs no browser action itself and only returns instructions. It also discloses the Enterprise-only API prerequisite, which prevents a failed path. It stops short of saying whether the target Everfit Cloud Browser must already be open or authenticated.

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 instruction is front-loaded and clear, but 'from ChatGPT, Claude or any AI agent' is filler that adds no decision value, and the trailing API/token paragraph with a date stamp reads as tangential reference material. The essential content could be two sentences instead of three dense ones.

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, read-only guidance tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields) and what it does not do (open anything). The remaining gap is prerequisites for the follow-up browser work, such as whether the Everfit Cloud Browser must already be open or logged in.

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 input schema has zero parameters, which is the baseline-4 case per the rubric. There is nothing for the description to disambiguate, and it does not waste words inventing parameter detail.

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 a specific resource (client overview in Everfit) and explicitly reframes what the tool actually returns: step-by-step instructions of screens, buttons and fields rather than the data itself. It also distinguishes itself from the cotlet_browser_* siblings by stating it 'opens nothing by itself'. The opening framing ('Get client overview') is slightly at odds with the real behavior (returns a how-to), but the very next clause resolves it.

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 workflow: call this to get the steps, then execute them with cotlet_browser_* tools in the user's Everfit Cloud Browser. It also preempts an alternative path by noting the official API is Enterprise-only, which steers the agent away from attempting API access. It does not name when to prefer everfit_list_clients or everfit_read_body_metrics instead, so no explicit exclusion among Everfit siblings.

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