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

Annotations already establish the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lower. The description still adds real value beyond them by disclosing that the tool performs no action itself, that its output is a per-screen procedure, and why browser automation is the route (no official MCP server, public API is beta and non-commercial).

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?

Front-loaded with the action, then the crucial "returns instructions / opens nothing" caveat, which is the right order. The final API-status sentence is slightly tangential but earns its place by explaining why the browser route exists instead of a direct integration.

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 produces (step-by-step screens/buttons/fields), what it does not do (opens nothing), and the required next step. Minor gap: it doesn't indicate whether the returned steps are tailored to a specific sales-report view or are generic across Skiddle screens.

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?

With zero parameters and 100% schema coverage, there is nothing for the description to disambiguate. The baseline of 4 applies; no parameter meaning is missing because none exist.

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 names a specific verb and resource ("Read ticket sales in the user's own Skiddle account") and immediately clarifies the non-obvious twist: it returns step-by-step instructions ("screens, buttons, fields") rather than performing the action, and "opens nothing by itself." This distinguishes it cleanly from the cotlet_browser_* executors, so an agent won't mistake it for the tool that actually fetches sales data.

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 sequencing guidance: call this first to get the procedure, then execute with cotlet_browser_* in the user's Skiddle Cloud Browser. What it lacks is an explicit comparison against siblings like cotlet_app_guide or the other skiddle_* guide tools (e.g., when to use this versus a generic app guide).

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