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

Annotations already cover the read-only, idempotent, non-destructive, closed-world profile, and the description adds genuinely new behavior: the return value is procedural guidance rather than fan data, and the call produces no side effects in the browser. It stops short of saying what account or browser-session state is required before the returned steps can be executed.

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?

Three compact sentences, front-loaded with what is returned and what is not performed. The trailing API note is slightly tangential but earns its place by explaining why a browser flow is necessary; some phrasing ('Returns how to do it in Bandsintown step by step') is awkward but not wasteful.

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 guide tool with no output schema, the definition covers what is returned, what it does not do, and the follow-up tools needed to complete the task. The remaining gap is prerequisite state: it does not say whether a Cloud Browser session must already be open or whether the user must be logged into Bandsintown.

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, so there is nothing for the description to disambiguate; baseline 4 applies. The only semantic input it could add is which account the stats come from, which it does address ('the user's own Bandsintown account').

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 outcome: it returns step-by-step instructions (screens, buttons, fields) for reaching fan stats in the user's own Bandsintown account. This usefully corrects the misleading name by making clear it is a guidance tool, not a data-fetching call, and it names the cotlet_browser_* siblings as the tools that actually perform the actions.

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: call this first to learn the steps, then execute them with the cotlet_browser_* tools in the Bandsintown Cloud Browser, and it explicitly notes the tool opens nothing by itself. It also rules out the official API as an alternative ('only reads: artist info and artist events'), though it does not contrast against the bandsintown_* mutation siblings directly.

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