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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, and the description stays consistent while adding genuine context: it explicitly states it "opens nothing by itself" and that it offloads execution to the browser tools. It also discloses an external constraint the annotations cannot — that PatientNow's REST APIs require an Essentials account with API access and a gateway key — which explains why a browser-driven path is used.

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 substantive content is front-loaded in two tight sentences covering what it returns and what to do next. The trailing API/gateway-key sentence is tangential background rather than invocation guidance, and the phrase "from ChatGPT, Claude or any AI agent" is filler, but neither buries the actionable information.

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 and no output schema, the description must describe the return value itself, and it does — a step-by-step walkthrough of screens, buttons, and fields. What is missing is any indication of scope or shape (e.g., how granular the steps are, whether it covers scheduling search specifically), but for a simple guidance tool this is close to sufficient.

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 closed object, so there is no parameter semantics to add; the baseline for a no-param tool applies. Nothing in the description misrepresents inputs, and the absence of inputs is consistent with a fixed-purpose guide 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 opening sentence says "Find free slots in the user's own PatientNow account," which reads like a data-returning search, but the next clause reveals it actually "Returns how to do it in PatientNow step by step (screens, buttons, fields) and opens nothing by itself." The real function — a procedural guide emitter, not a slot query — is stated clearly but only after the misleading lead, so an agent scanning the first line could mis-select 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 does establish the workflow: get the guide here, then execute it "with the cotlet_browser_* tools in the user's PatientNow Cloud Browser," which is a useful sequencing instruction. However, it names no alternative or exclusion — sibling guide tool cotlet_app_guide and the action tools like patientnow_book_appointment are never compared against, so the agent must infer when this beats them.

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