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

Beyond the readOnly/destructive/idempotent annotations, it discloses the concrete return shape (step-by-step screens, buttons, fields) and that nothing is opened automatically, which prevents an agent from assuming a side effect. The note that Bandsintown's public API is read-only explains why a browser flow is required. It does not specify error or auth behavior if the user lacks a Bandsintown account.

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 key constraint ('returns how to do it... opens nothing by itself') is front-loaded, which is good. However, 'from ChatGPT, Claude or any AI agent' is filler, and the closing API sentence is long and only marginally actionable for invocation.

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 confirmed annotations, the definition covers what an agent needs: what it returns, that it has no side effects, and which tools carry out the actual deletion. A short statement of the exact response format or prerequisites for the user's account would make it fully complete.

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 no parameters, so the schema carries no semantics to supplement; baseline is 4. The description adds nothing about parameters, but nothing is needed.

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 makes clear that this tool does not perform a deletion but returns step-by-step instructions (screens, buttons, fields) for deleting an event in the user's own Bandsintown account. It implicitly separates itself from siblings like bandsintown_add_event and bandsintown_update_event, though it never names them. The only friction is the name itself, which reads as a mutation and must be corrected by the description.

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 context: use this to learn how to delete an event in the user's own account, then execute with the cotlet_browser_* tools in the Cloud Browser. It also states the negative case ('opens nothing by itself'), so an agent won't expect the deletion to happen here. It stops short of explicitly contrasting with cotlet_app_guide or update_event as alternatives.

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