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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses the key behavioral fact that the tool 'opens nothing by itself' and returns descriptive guidance (screens, buttons, fields). It also explains why browser automation is required, citing the absence of any official API or Zapier app. It stops short of saying whether the browser session must already be open or what happens if the user has no Portrait Care account.

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 next-step routing are front-loaded, but the final sentence is bloated with a meta-quotation ('a fully integrated platform with no mention of third-party integrations') and a verification date that reads oddly (9 Nov 2026). The claim that no API exists could be stated in a fraction of the space.

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?

For a zero-parameter guidance tool with annotations covering the safety profile and no output schema, the definition supplies the action, the return nature, and the follow-up tooling. Minor gaps remain around preconditions such as an authenticated Cloud Browser session.

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 with full schema coverage, so the baseline is 4. There is nothing parameter-level for the description to add, and it correctly does not invent inputs.

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 (find lapsed patients) and scopes it to the user's own Portrait Care account, and it distinguishes itself from the cotlet_browser_* tools by saying it returns instructions rather than acting. The opening sentence implies the tool performs the lookup, while the second sentence clarifies it only returns step-by-step guidance — a mild tension an agent must resolve by reading further.

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 Portrait Care steps, then execute them with cotlet_browser_* in the Cloud Browser. It does not name an explicit when-not or contrast itself with cotlet_app_guide or portrait_care_list_patients, so the routing is clear but not complete.

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