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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses that the return is procedural instructions (screens, buttons, fields) rather than data, that it performs no action itself, and that a follow-up browser step is required. This is exactly the behavioral context an agent cannot get from structured fields.

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 with the purpose front-loaded and the mechanism/sequencing detail following. It is dense but every sentence carries operational meaning; the 'no public API' note is minor but relevant to why browser tools are needed.

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 and no output schema, the description compensates by describing the nature of the returned content and the required follow-up step. It is nearly complete; the exact structure of the returned instructions could be spelled out further but is adequately conveyed.

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 and schema coverage is 100%, so the baseline applies. There is nothing parameter-specific for the description to add, and it does not confuse the picture.

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 ('List recipe books') and scopes it to 'the user's own CoachingPortal account', which separates it from siblings like delete_recipe_book or assign_recipe_book. It is clear but does not explicitly name which sibling to use for other operations.

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 strong mechanism-based usage rule: this tool returns step-by-step instructions and 'opens nothing by itself', and the actual operation is done afterwards with the cotlet_browser_* tools. That tells the agent how the tool fits into a workflow, though it stops short of explicit when-not-to-use exclusions.

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