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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, and the description reinforces this with "opens nothing by itself," so no contradiction exists. It goes beyond the annotations by disclosing the return content (screens, buttons, fields), the fact that it performs no side effect on PatientNow, and the prerequisite path for the actual operation plus the API-access gate. Missing is what happens if no Cloud Browser session exists.

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 first two sentences are well front-loaded and do the real work. The third sentence about PatientNow's REST APIs and the dated gateway-key check is tangential for a zero-parameter guidance tool and reads like justification clutter rather than actionable instruction, diluting an otherwise tight definition.

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 carries the whole burden, and it covers the return nature (step-by-step instructions), the no-side-effect guarantee, and the follow-up tools needed to execute. It falls short only on operational prerequisites such as needing an open PatientNow Cloud Browser session and what the agent should do if the steps cannot be completed.

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 object with additionalProperties=false, so there is no parameter meaning to convey. Baseline of 4 applies; the description adds no erroneous parameter hints.

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?

States a specific verb and resource ("List patients in the user's own PatientNow account") and then corrects the natural assumption by saying it "Returns how to do it in PatientNow step by step... and opens nothing by itself." This makes the guidance-vs-execution distinction explicit, though the leading "List patients" phrasing still reads like data retrieval and the description never differentiates itself from siblings such as patientnow_find_lapsed_patients.

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?

The workflow is implied clearly: get the steps here first, then perform them with the cotlet_browser_* tools in the Cloud Browser. The trailing note about the official REST API (Essentials account with API access enabled, plus a gateway key) explains indirectly why this path may be preferred. However, there is no explicit "use this when / not when" statement or named alternative, so the agent must infer the selection criteria.

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