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

Annotations already establish readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so safety is partly covered. The description adds substantial extra context: event is a non-public draft, visibility only changes on publish, the action is reversible via a single delete_event call, no confirmation prompt is needed, and a Cotlet API key with app access is required. That is a rich behavioral profile, though it does not describe the response payload.

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 critical fact (draft, nothing public until publish) is front-loaded, and every sentence conveys non-redundant information about behavior, sourcing, or auth. There is minor overlap between the opening line and 'Saves a new event as a draft', keeping it just below maximum.

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-behavior burden, and it does: it explains the resulting state (draft under Drafts), visibility implications, reversibility, and authorization needs. For an eight-parameter create tool this is complete enough for correct invocation.

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%, so the schema already documents all eight parameters, including 'One link must be tickets' and the venue/custom_location split. The description largely restates these constraints ('Attach a venue from search_venues or pass custom_location', 'One ticket link must carry the Tickets label') rather than adding format or value guidance, landing at the baseline.

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+resource ('Saves a new event as a draft') and immediately distinguishes it from siblings by emphasizing the draft/not-public state, implicitly contrasting with publish_event. An agent can tell it apart from bandsintown_publish_event, bandsintown_update_event, and bandsintown_delete_event without opening a schema.

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?

Explicitly routes the agent: 'Attach a venue from search_venues or pass custom_location' names the alternative source, and the publish/delete references clarify the lifecycle position. It even states the calling policy ('runs without asking first'), so the when-to-use and when-not-to-prompt conditions are both covered.

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