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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false. The description adds genuinely new behavioral context beyond them: the tool performs no navigation and opens nothing, it returns procedural guidance rather than data, and there is no general-purpose vendor API to fall back on. It stops short of saying anything about the shape or length of the returned guidance.

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 clauses are front-loaded and earn their place, and the pointer to the browser tools is essential. However, the trailing "TotalCoaching's official API" sentence with a dated vendor-source disclaimer reads as boilerplate and competes for attention with the operational instruction, adding bulk without helping the agent act.

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?

There is no output schema and no parameters, so the description should carry the full load, and it does explain what is returned (step-by-step screens, buttons, fields) and what is not (no automatic navigation). The notable gap is scope: with zero parameters, it never says how a specific client's calendar is identified, whether context comes from the session, a prior list call, or the browser, leaving the agent unsure how to target the right client.

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 of 4 applies. Nothing in the description needs to decode parameter meaning, and the schema's empty object is consistent with a parameterless guidance 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 description names a specific verb+resource ("Read client training calendar") and then clarifies the actual output: a step-by-step procedure of screens, buttons and fields. The one wrinkle is that the verb-first phrasing suggests it returns calendar data, while it actually returns instructions on how to read the calendar; the clarification sentence resolves this, so an agent can still tell what it gets.

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 states the workflow explicitly: call this to get the procedure, then execute it with cotlet_browser_* tools in the Cloud Browser. It also flags that it "opens nothing by itself", preventing an agent from expecting the read to have happened. It does not contrast itself against cotlet_app_guide or totalcoaching_read_client_profile, so sibling routing is left partly to inference.

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