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

Annotations declare readOnly, idempotent, non-destructive and closed-world, and the description adds genuinely non-obvious behavior on top: the tool opens nothing by itself, returns step-by-step screens/buttons/fields, and must be followed by browser automation. That workflow hand-off is the key trait an agent could not get from annotations alone. It does not mention authentication or session prerequisites for the browser step.

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?

Purpose and scope are front-loaded, which is good, but the single run-on sentence chains four ideas with semicolons and an awkward mid-sentence aside ('and opens nothing by itself'), making the critical 'returns instructions, not data' point easy to skim past. A short second sentence separating the follow-up browser step would read better.

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 tool with no output schema, the description covers what it returns (step-by-step screens, buttons, fields), what it does not do (opens nothing), and what to do next (cotlet_browser_*). That is close to sufficient; only the absence of any note on browser session or account prerequisites leaves a small gap.

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 applies. The description correctly implies no inputs are needed by framing the call as a pure instruction retrieval.

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 specific verb and resource (get grocery list) scoped to the user's own CoachingPortal account, and immediately clarifies the unusual delivery mechanism: it returns navigation steps rather than the data. It does not distinguish itself from plausible siblings such as list_meal_plans or list_recipe_books, so an agent must still infer that this is a UI-walkthrough helper rather than a data-listing tool.

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 context for use: call this when working from ChatGPT, Claude or any AI agent, then execute the returned steps with the cotlet_browser_* tools in the user's Cloud Browser. It also pre-empts the obvious 'why not just use the API' question by stating that CoachingPortal publishes no public API. It stops short of naming when-not-to-use or a sibling alternative.

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