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

Adds real context beyond annotations: it 'opens nothing by itself', returns a UI walkthrough (screens, buttons, fields), and must be followed by browser tools. This confirms and explains the readOnlyHint=true annotation rather than contradicting it. It does not describe output length or failure cases, keeping it below a 5.

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?

Two sentences, front-loaded with the action and the no-side-effect guarantee, then the continuation path. The API note is short and earns its place by preventing a wasted API-lookup attempt. Minor density comes from cramming three ideas into the first sentence.

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, this covers what it returns, that it has no side effects, and how to complete the task afterward. The main residual gap is that it does not distinguish itself from the recipe-book management sibling, but nothing needed to invoke it correctly is missing.

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 nothing for the description to disambiguate and the baseline of 4 applies. It correctly implies the target account is the caller's own CoachingPortal account rather than an arbitrary one.

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+resource ('Assign recipe book in the user's own CoachingPortal account') and immediately clarifies the tool returns step-by-step instructions rather than performing the action. It could be sharper about how it differs from siblings like coachingportal_manage_recipe_book, but an agent can tell this is a guidance-producing tool, not a mutation.

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 follow-up path — use the cotlet_browser_* tools in the Cloud Browser to actually perform the assignment — and notes there is no public API, which rules out an API route. However, it never states when to choose this over sibling tools such as coachingportal_manage_recipe_book or coachingportal_assign_program, so usage is implied rather than decided.

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