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

Annotations already cover read-only/safe/readOnlyHint, so the bar is lower. The description adds real context beyond them: results are sorted soonest-first, items carry a published/draft status, and it discloses a prerequisite (Cotlet API key with access to this app).

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 and reasonably short, but the phrase 'with date, venue, ticket links and status' is effectively repeated in the second sentence ('with date, venue, ticket links and whether each is published or a draft'). That duplication costs it a point.

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 no output schema, the description carries the return-value burden and does list the salient fields (date, venue, ticket links, published/draft), plus sorting, filtering and auth needs. It is complete enough to call correctly, only missing pagination/limit behavior.

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?

Schema coverage is 100%, so the schema fully documents to/from/status/artist_id including defaults. The description restates the status and date-range filtering behavior but adds no format or value detail beyond the schema, matching the baseline for full coverage.

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?

States a specific verb (list/returns) and resource (events of one artist page), with scope (soonest first) that distinguishes it from bandsintown_get_event. An agent can identify this as the collection-listing tool versus the single-event retrieval tool.

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?

Gives clear context: filter by status or date range, use the returned event_id with other tools. It does not explicitly contrast with siblings like get_event or explain when NOT to use it, but the usage intent is unambiguous.

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