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

Annotations already declare readOnly, idempotent and non-destructive; the description adds meaningful context beyond them — it explicitly says the tool opens nothing and returns screens/buttons/fields, and notes the official API is plan-gated. This is consistent with readOnlyHint=true and explains why a guide tool exists instead of an API call.

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 workflow sentence is front-loaded and useful, but filler like "from ChatGPT, Claude or any AI agent" and the lengthy API plan/licensing aside dilute the core message. It is adequate but not tight.

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, no-output-schema guide tool whose annotations cover the safety profile, the description is nearly complete: it says what it returns, what it does not do, and what to do next. Only the exact shape of the returned guide and handling of unsupported plans is left unspecified.

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 description carries no parameter burden and the baseline of 4 applies. No misleading parameter expectations are introduced.

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 (schedule an appointment in Trainerize) and clarifies that it returns step-by-step instructions rather than performing the action. The name implies the tool schedules, while the body says it "opens nothing by itself" — a slight internal tension, though the real purpose (returning a guide) is eventually clear and distinguished from the cotlet_browser_* siblings that do the actual work.

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 workflow: call this, then execute with cotlet_browser_* in the user's Cloud Browser. That folds use into a sequence but does not explain when to choose this over directly navigating Trainerize with the browser tools, nor how it relates to other trainerize_* tools or cotlet_app_guide.

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