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

The annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-redundant behavior: 'opens nothing by itself' and the granularity of the returned guidance (screens, buttons, fields). The note that HappyFox has a REST API but no official MCP server explains why browser automation is the required follow-up.

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 core claim and the handoff to cotlet_browser_* tools are front-loaded and earn their place. The trailing sentence about HappyFox's REST API version and the 'checked 20 Oct 2026' datestamp add bulk and a stale date that an agent does not need in order to invoke the tool, and 'from ChatGPT, Claude or any AI agent' is filler.

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 carries the burden of explaining what comes back, and it does so ('how to do it step by step (screens, buttons, fields)'). It does not mention prerequisites such as an existing logged-in Cloud Browser session or authentication state, which is the one gap for a guidance-then-automate tool.

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 schema coverage is 100%, so the baseline applies. The description correctly implies no inputs are needed, consistent with the empty object schema.

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 (add a private note) and immediately clarifies the crucial twist: the tool returns step-by-step instructions rather than performing the action. That distinguishes it from action-taking siblings such as happyfox_reply_to_ticket, though it never names or contrasts those siblings directly.

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 an explicit follow-up path — 'then do it with the cotlet_browser_* tools in the user's HappyFox Cloud Browser' — which tells the agent exactly how to complete the workflow. It stops short of stating when to prefer this over a direct-API sibling like happyfox_update_ticket, and offers no exclusions.

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