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

The description explicitly says it 'opens nothing by itself' and only returns instructions, which is exactly the context needed to reconcile a 'manage' name with readOnlyHint=true and destructiveHint=false — no contradiction. It also discloses the missing-API constraint that forces the browser-tool follow-up, though it says nothing about whether the returned steps depend on account state or permissions.

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 is front-loaded and the second sentence carries the key operational detail. The closing sentence about the official API is awkwardly phrased and the 'from ChatGPT, Claude or any AI agent' clause adds bulk without decision-relevant information.

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 tool the description covers the return shape (screens, buttons, fields) and the follow-up path. What it omits is which workout-block actions the guidance actually covers and any precondition (e.g. being signed in), which an agent needs to know before promising the user the task is doable this way.

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 and the description correctly implies no input is required, so there is no parameter meaning to add. Baseline applies.

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 states a concrete resource (workout block in the user's own CoachingPortal account) and clarifies the surprising mechanic: it returns step-by-step instructions rather than performing the action. It does not differentiate itself from near siblings such as coachingportal_manage_personal_workout or coachingportal_list_workout_blocks, and 'manage' leaves which operations (create/edit/delete/reorder) are covered unstated.

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 workflow: call this for the steps, then execute with cotlet_browser_* tools in the Cloud Browser, and it notes there is no public API alternative. However, it never states when NOT to use it or names a sibling for related tasks (listing blocks, personal workouts), so an agent must infer routing.

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