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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description still adds real value: it discloses that the output is procedural instructions rather than data and that no navigation occurs. Minor gaps remain — no mention of whether the guide reflects a live UI or cached content, and the 'checked 11 Oct 2026' date is an unexplained future date.

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 point — returns instructions, does not act — is buried mid-sentence rather than front-loaded. Filler like 'from ChatGPT, Claude or any AI agent' and the redundant 'Fresha's official API: Fresha has no public API' phrasing dilute two otherwise useful sentences.

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 full annotation coverage, the only thing an agent needs to know is what comes back and what to do next — both are stated. It would be complete at 5 with a note on session prerequisites or the failure mode when the Fresha browser is unavailable.

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 nothing for the description to disambiguate and the baseline of 4 applies. The description correctly does not invent parameter behavior.

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 concrete operation and, crucially, corrects the misleading name: it does not return appointment data, it returns a step-by-step guide of screens, buttons and fields. That distinction from data-returning siblings like list_appointments is stated explicitly, though the phrasing 'Returns how to do it in Fresha step by step' is clunky.

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 clear sequencing: call this to get the instructions, then execute with the cotlet_browser_* tools in the user's Fresha Cloud Browser, and it notes the tool itself 'opens nothing by itself.' What it lacks is an explicit statement of when to prefer the non-Fresha list_appointments sibling or what to do when the Fresha browser session is not available.

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