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

Annotations already cover read-only/idempotent/non-destructive behavior. The description adds useful output behavior by stating that it returns set times, stages, and artists, which is especially important since there is no output schema; it also gives example queries that imply name-based lookup. It does not discuss edge cases like empty results or filter combination semantics, but no annotation contradiction exists.

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 front-loaded sentences: the core action and return content come first, followed by two illustrative questions. There is no filler or redundant restatement of the title/schema.

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 lookup tool with four optional filters and no output schema, the description covers purpose, return values, and typical usage. A small gap is the lack of guidance on event_id vs event_name precedence or how stage/artist filters combine, but these are optional refinements and the examples make the common cases unambiguous.

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?

All four parameters have schema descriptions (100% coverage), so the baseline is met. The description's example questions enrich the semantics by mapping natural-language requests to artist and event_name, which helps the agent see how to populate those fields; stage is left to the schema.

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?

The description opens with a specific verb and resource ('Get the DJ/artist schedule'), then enumerates the returned content ('set times, stages, and artists'). This clearly differentiates it from siblings like get_event_details and get_now_playing by focusing on schedule/lineup rather than general event or current-play info.

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 'Use this to answer questions like...' sentence gives concrete query patterns that signal when the tool is appropriate. However, it does not explicitly name alternative tools or state when not to use this tool, so it stops short of full routing guidance.

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