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

Annotations already declare the full safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add behavioral value by disclosing what the response contains (invitees and attendees) and the artist-connection scope, but says nothing about ordering, pagination, or whether unpublished/draft events appear.

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?

Two compact sentences, no filler, with the content scope front-loaded and the eligibility constraint appended. Every clause carries information the agent needs.

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 sketch the payload ('who is invited and who is coming'). It is nearly complete for a single-optional-parameter read tool, but omits ordering/format details an agent might want.

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 description coverage is 100%, and the single 'artist' parameter is fully documented in the schema, including its conditional requirement on label connections. The description adds no parameter-level information, so the baseline 3 is correct.

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?

It states a concrete resource — shows, release parties, and listening parties the artist has posted — plus the payload ('who is invited and who is coming'), so the agent knows exactly what this returns. It does not explicitly differentiate itself from read/write siblings like save_event or cancel_event, so it stops short of a 5.

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?

The scoping rule 'Artist connections only' tells the agent one condition under which this applies, which is useful guidance. However, it never names an alternative (e.g. save_event for creating one) or describes when this is preferable over other listing tools, leaving usage largely inferred.

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