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

Beyond the annotations (readOnlyHint, idempotent, non-destructive), the description adds the critical trait that the tool 'opens nothing by itself' — a non-obvious behavior that prevents an agent from assuming queues are actually fetched. It also notes the environment handoff to the browser tools, though it says nothing about output format or length of the returned steps.

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 behavioral point and the handoff to cotlet_browser_* are front-loaded and useful, but the closing paragraph about HappyFox's REST API version 1.1 and the absence of an official MCP server is tangential background that does not help an agent decide or act, and the point about 'no MCP server' is never used.

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 guide tool with no output schema, the description covers what it returns (steps, screens, buttons, fields), that it performs no action, and what to do next. The only gap is the exact shape/length of the returned procedure, which matters mildly for planning.

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, which is the baseline-4 case; there are no parameter semantics to explain and the description correctly implies nothing needs to be supplied.

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 gives a concrete verb and resource — it returns step-by-step instructions (screens, buttons, fields) for viewing queues in the user's HappyFox account — and clarifies that it opens nothing itself, which is essential because the name 'list_queues' implies live data retrieval. It stops short of a 5 because the opening phrase still echoes the tool name and the actual deliverable (a guide, not a list) only becomes clear in the second sentence.

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?

Clear sequencing guidance is provided: call this first to get the procedure, then perform it with cotlet_browser_* tools in the HappyFox Cloud Browser. There are no explicit exclusions (e.g., when to use cotlet_app_guide or cotlet_apps instead), which keeps it from a 5.

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