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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and closed-world, so the safety profile is covered structurally. The description adds genuinely useful context beyond that: the tool produces instructions (screens, buttons, fields) and never mutates anything itself, and no official API exists so browser automation is the follow-up path. It stops short of describing output shape, coverage limits, or failure modes when the requested program does not exist.

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 most consequential fact, that this only returns instructions and performs nothing, is front-loaded in the first two sentences. The trailing 'CoachingPortal's official API: CoachingPortal publishes no public API' is slightly redundant in phrasing but still carries the actionable justification for the browser follow-up.

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, output-schema-less tool, the definition covers what is returned (step-by-step screens, buttons, fields) and the required next step (cotlet_browser_* tools). It does not state what happens if the user lacks a matching program or is unauthorized, which would matter for a browser-driven follow-up flow.

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?

There are zero parameters and full schema coverage, so the baseline is 4. The description introduces no parameter expectations that would confuse the agent, which is correct for a no-argument 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?

States a specific verb and resource ('Duplicate program') and scopes it to 'the user's own CoachingPortal account', then clarifies the tool returns step-by-step instructions rather than performing the action. What is missing is any explicit contrast with program-creation/assignment siblings (e.g. create_program_template, assign_program), so the agent must infer that this is the guide-only path.

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?

The definition explains the workflow role clearly: it 'opens nothing by itself' and the agent must then act with the cotlet_browser_* tools in the Cloud Browser, and it notes the absence of a public API. It gives clear context for when this tool applies but offers no explicit exclusion criteria versus other program-management tools.

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