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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so safety is covered. The description adds the non-obvious behavioral fact that the tool 'opens nothing by itself' — i.e. it is advisory only and requires a follow-up browser call — plus why the API route is unavailable, which justifies the browser path.

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?

Front-loaded with the outcome and then the mechanism; every clause carries information (what is returned, what is not done, what to do next, why not via API). The single long sentence with a semicolon is dense and slightly awkward to parse, but there is no 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 parameters, no output schema, and annotations covering the safety profile, the remaining burden is to explain the return shape and the follow-up workflow — both are addressed (step-by-step screens/buttons/fields, then browser tools). The only gap is not naming which sibling tool to choose if the user actually wants the other appointment/wait-list data.

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. Nothing in the description is needed to clarify inputs, and it does not waste space re-describing an empty schema.

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 unscheduled patients in the user's own Jane App account') and then corrects the likely misreading by explaining the tool returns step-by-step instructions rather than the patient data itself. It is not explicitly differentiated from near-neighbours like jane_app_list_appointments or jane_app_read_the_wait_list, which an agent would have to infer from the resource name.

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?

Gives a clear two-step workflow: call this to get the screens/buttons/fields, then execute with the cotlet_browser_* tools in the Cloud Browser. It also rules out the API path by noting Jane's API is partner-only. It stops short of saying when to prefer this over the sibling list/read tools.

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