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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description resolves the apparent conflict with the name by stating it 'opens nothing by itself' and only returns instructions, so no annotation contradiction. It adds genuinely useful context — what the return looks like (screens, buttons, fields) and the Cloud Browser prerequisite — though it could say more about what happens if the user has no active browser session.

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 workflow-critical information (what it returns, that it does nothing itself, and which tools finish the job) is front-loaded in the first two sentences. Some filler is present, such as 'from ChatGPT, Claude or any AI agent' and the API 'checked 11 Oct 2026' date, which add bulk without changing how an agent invokes the tool.

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 zero parameters, no output schema, and full annotation coverage, the description carries the right burden: it explains the return value, the prerequisite environment, and the follow-up tools. The only gap is the absence of any note about failure modes (e.g., no logged-in Bandsintown account or no open Cloud Browser session).

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; the baseline of 4 applies. No parameter-level meaning is missing because the input schema is empty and closed (additionalProperties: false).

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 (send a fan message in the user's own Bandsintown account) and immediately clarifies the actual behavior: it returns step-by-step instructions rather than performing the send. It also differentiates itself from the cotlet_browser_* siblings by naming them as the tools that execute the action.

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?

Usage is explicit: call this first to get the screen/button/field walkthrough, then perform it with cotlet_browser_* in the Bandsintown Cloud Browser. It also justifies the two-step approach by noting the official API is read-only, which implicitly explains why browser automation is needed. It stops short of stating when NOT to use it, but the workflow is unambiguous.

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