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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false. The description adds a real behavioral fact beyond them: it requires the user's Cotlet API key with access to this app, which is important auth context for invocation.

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 first two sentences are redundant, repeating the same fact ('RSVPs per show from Insights, the same figures as Events Performance') twice. The scoping and auth guidance is useful but the duplicate framing wastes space.

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?

For a read-only stats tool with full schema coverage and no output schema, the description covers scope, default behavior, and auth requirements adequately. A brief note on return shape would complete it, but the essentials are present.

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 event_id and artist_id are already documented, and the description largely restates the event_id default. Baseline 3 applies since the schema carries the parameter burden.

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 (get RSVPs per show) and clarifies the exact metrics returned, tying it to the Insights 'Events Performance' view. This distinguishes it topically from siblings like get_follower_stats and get_top_markets, though it never names them.

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 conditional usage: 'Pass event_id for one show, or leave it out for all upcoming shows.' This tells the agent how to scope the call. It stops short of naming alternative sibling tools or when-not-to-use cases.

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