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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description confirms the tool is purely advisory and performs no action. It also discloses the shape of the returned content (screens, buttons, fields) and points to the browser tools that actually execute the work, which is meaningful context beyond the annotations. It does not say how the response is structured or whether the steps vary by account configuration.

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 critical facts are front-loaded: what it returns and that it performs nothing. The sentence is long and runs three clauses together, and the trailing line about CoachingPortal publishing no public API is only loosely related to invoking this tool. It is still compact enough to read in one pass.

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 zero parameters, no output schema, and safety fully covered by annotations, the remaining burden is telling the agent what comes back and what to do next, which it does. The main gap is that it never states prerequisites, such as needing an existing program template or an active Cloud Browser session, before the returned steps can be followed.

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 there is no parameter semantics to explain and the baseline of 4 applies. Nothing in the description contradicts the 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?

The description states a concrete outcome: it returns step-by-step CoachingPortal instructions (screens, buttons, fields) for assigning a program, and explicitly says it 'opens nothing by itself.' This makes the guidance-only nature unambiguous despite a name that sounds like a mutation. It does not explicitly distinguish itself from close siblings such as coachingportal_assign_meal_plan or coachingportal_assign_recipe_book, leaving that separation to the tool names.

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 clear operating sequence: call this to obtain the manual steps, then perform them with the cotlet_browser_* tools in the user's CoachingPortal Cloud Browser. The exclusion ('opens nothing by itself') tells the agent not to expect the assignment to be completed here. It stops short of stating when to prefer this over a native API path or how to handle a missing program template.

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