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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false. The description adds non-obvious behavior beyond them: the tool returns instructions (screens, buttons, fields) rather than performing the action, and the actual execution happens through the browser tools. The API paragraph explains why browser automation is necessary, which is useful context, though it doesn't cover prerequisites like needing an open HappyFox tab.

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 key fact — this returns instructions, not performs the action — is front-loaded in the first sentence. The third sentence about HappyFox's REST API is marginally useful rationale but slightly tangential; otherwise the text is dense and earns its space.

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, read-only guidance tool with no output schema, it covers what is returned and the follow-up workflow well. However, it omits how the target canned action and ticket are determined without parameters, and any state requirements (e.g., an already-open HappyFox ticket in the browser), which an agent would need before calling it.

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, which is the baseline-4 case. The description does not explain how the specific canned action is identified given no parameters — presumably from current browser context — but with an empty schema there is little for the description to elaborate on.

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 — returning step-by-step instructions for applying a canned action — and immediately corrects the misleading verb in the name by saying it 'opens nothing by itself.' An agent can tell that this is a guidance tool, not an executor, without opening anything else.

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 explicitly names the follow-up path: 'then do it with the cotlet_browser_* tools in the user's HappyFox Cloud Browser,' which is a concrete alternative/next step. It doesn't cover exclusions such as when to prefer cotlet_app_guide or the native happyfox_* ticket tools, but the core when-to-use routing is present.

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