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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely non-structured context: the result includes drafts that are 'saved, not posted, seen by nobody else' and shows who is invited versus who is coming, plus an authorization constraint (artist connections only). That is meaningful disclosure beyond the annotations.

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 sentences, front-loaded with what is returned and followed by the access constraint. The nested parenthetical about drafts is slightly dense but each clause carries information; nothing is padding.

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 does the work of describing the return payload (events, invitees, attendees, drafts) and the connection requirement. For a single-optional-parameter read tool this is close to complete; only pagination or ordering behavior is unaddressed.

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 thoroughly documented in the schema itself, including its label-connection requirement. The description adds no parameter-level syntax or format detail, so the baseline of 3 is appropriate.

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 resource (shows, release parties, listening parties) scoped to what the artist has posted, which clearly separates it from the write-side siblings save_event and cancel_event. It never names a sibling explicitly, so it stops short of full differentiation, but the verb+resource is unambiguous.

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 description supplies a real usage constraint — 'Artist connections only: Scene is between artists' — which tells the agent which connection context is valid. However, it gives no guidance on when to prefer this over save_event, cancel_event, or other listing tools, so the when/when-not routing is only implied.

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