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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces this meaningfully by saying it 'opens nothing by itself' and returns textual instructions instead. It also discloses the external constraint on Trainerize's official API, which explains the tool's existence. Minor noise ('ChatGPT, Claude or any AI agent') dilutes but does not undermine the disclosure.

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 core message ('returns steps, opens nothing, then use cotlet_browser_* tools') is front-loaded, but the first clause about ChatGPT/Claude/any AI agent is filler and the API-plan sentence is a long run-on tangent. The density is acceptable but could be tightened considerably.

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 read-only annotations, the description supplies what an agent needs: what it returns, that it performs no side effects, and what to do next. It could be stronger by naming the specific sibling guide tool or noting prerequisites such as an authenticated Cloud Browser session.

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 and there is nothing for the description to compensate for. The description does not need to describe inputs, and its focus on outputs and workflow is appropriate.

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 the resource (program assignment in the user's Trainerize account) and, crucially, clarifies that it returns step-by-step instructions rather than performing the action itself. That distinction is essential because the tool name 'assign_program' implies an action. It does not, however, differentiate itself from similar guide-style siblings such as cotlet_app_guide.

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 clear sequencing guidance: call this to get the step-by-step procedure, then execute it with the cotlet_browser_* tools in the Cloud Browser. It explains why the browser path is needed (API limited to Studio/Enterprise or the FitMetrics add-on). It stops short of stating when not to use it or naming an alternative guide tool.

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