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

Annotations already declare readOnlyHint=true and openWorldHint=false; the description reinforces this with 'opens nothing by itself', which removes any doubt that the tool mutates the account. It also discloses the return shape (step-by-step screens, buttons, fields) even though no output schema exists, and flags the external dependency on the Phorest Cloud Browser. It does not cover failure modes, e.g. what happens if the browser session is not open.

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 behavioral core ('returns steps, opens nothing, then use cotlet_browser_*') is front-loaded and useful, but 'from ChatGPT, Claude or any AI agent' is promotional filler and the trailing API parenthetical with a check date is long for its value. Roughly a third of the text 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 zero parameters and no output schema, the description carries the burden of explaining the return, which it does (screens, buttons, fields) and follows through on the handoff to the browser tools. Minor gaps remain: no statement of whether the Phorest Cloud Browser must be opened first, and no indication of how the guidance is scoped to the user's account.

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 (schema coverage 100%, empty object), so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies no arguments are needed to request the guidance.

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 resource (free slots in the user's own Phorest account) and, crucially, clarifies that the tool does not itself return slots but 'Returns how to do it in Phorest step by step (screens, buttons, fields)'. That corrects the misleading name/title, but the correction only lands on a careful read, so it falls short of a clean verb+resource statement.

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 routes the agent explicitly: call this first, 'then do it with the cotlet_browser_* tools in the user's Phorest Cloud Browser', and it explains why the official API is not the path (credentials only via Phorest Support, requires own dev team). It stops short of naming a direct alternative such as cotlet_app_guide or phorest_book_appointment, or stating prerequisites like whether the browser must already be open.

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