setlist_get_venue_setlists

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

Annotations already declare readOnlyHint=true, so the description adds value by detailing pagination, ordering (most recent first), and the presence of a `url` field. It also clarifies the attribution requirement. No contradictions.

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: first states purpose and pagination, second gives critical attribution instruction. No wasted words, front-loaded with essential information.

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 paginated listing tool with 2 parameters and no output schema, the description adequately covers how to use it (venue ID, pagination) and what to expect (results with url, order). It lacks details on other possible fields but is sufficient.

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 coverage is 100%, so the schema already describes both parameters. The description adds context that `p` is for pagination (already in schema) and that results include a url. This adds some value but does not significantly surpass the schema's 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?

The description clearly states the tool retrieves setlists performed at a venue by venue ID, with results ordered most recent first. It distinguishes itself from siblings like setlist_get_venue (venue details) and setlist_get_artist_setlists (by artist).

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?

Provides explicit instruction on pagination via `p` and mandates attribution by citing a clickable source link. Does not explicitly list when not to use or alternatives, but sibling context implies its specific use case.

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