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

Annotations already declare a safe, read-only, idempotent, closed-world operation, so the bar is lower; the description still adds genuine context by stating it 'opens nothing by itself' and returns instructions instead of data. The note that Portrait Care publishes no API or developer docs explains why browser automation is required, which is material planning information beyond the annotations.

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 purpose and the caller flow are front-loaded, but the final sentence is bloated — an embedded self-quote and a dated verification stamp ('checked 9 Nov 2026') consume space without helping an agent decide or act. The 'from ChatGPT, Claude or any AI agent' clause is filler.

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 output schema, the description carries the burden of describing the return value, and it does so ('returns how to do it step by step (screens, buttons, fields)'). For a zero-parameter guidance tool this is nearly complete; only the expected response shape and any follow-up confirmation step are unaddressed.

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 the baseline is 4 and there is nothing the description could add on parameter meaning. It does not mislead about inputs or imply hidden options.

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 a specific verb and resource ('List patients in the user's own Portrait Care account') and clarifies the non-obvious nature of the tool: it returns step-by-step UI instructions rather than patient data. It does not differentiate itself from siblings such as portrait_care_find_lapsed_patients, so an agent must infer that distinction from names alone.

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 a usable pattern — call this first, then act via the cotlet_browser_* tools in the Portrait Care Cloud Browser. However, it never states when to pick this over the other portrait_care_* listing tools, nor what to do if the user lacks a Portrait Care account.

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