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

The description explicitly discloses that the tool 'opens nothing by itself', which reinforces and explains the readOnlyHint=true annotation rather than merely restating it, and it discloses what is returned (step-by-step screens, buttons, fields). The API paragraph adds genuine context about why browser automation is required (Enterprise-only token by email). It does not cover preconditions such as the user being logged into Everfit, so it is not exhaustive.

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 behavior and the handoff to browser tools are front-loaded in the first two sentences. The third sentence about Everfit's official API is supporting rationale but is somewhat tangential and carries noise like '(checked 11 Oct 2026)', which does not help an agent decide or invoke.

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, no output schema, and annotations already covering the safety profile, the description supplies what is missing: what is returned and what to do next. Only preconditions and failure behavior are absent, which are minor for a zero-argument guidance 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, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies a parameterless, self-contained lookup rather than a call that needs a program ID or client ID, which is itself useful disambiguation.

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 the outcome ('Assign program in the user's own Everfit account') and then states precisely what the tool itself produces: 'Returns how to do it in Everfit step by step (screens, buttons, fields)'. The lead clause reads as if the tool performs the assignment, so the correction only lands in the second sentence, but the net meaning is unambiguous and clearly distinct from the cotlet_browser_* siblings.

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 an explicit usage sequence: call this to get the steps, then 'do it with the cotlet_browser_* tools in the user's Everfit Cloud Browser', which tells the agent this is the planning step in a two-phase workflow. It does not state exclusions (e.g. when cotlet_app_guide or the Everfit API path would be preferred beyond the Enterprise note), so it stops short of full when/when-not guidance.

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