setlist_get_setlist_version

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

Annotations already declare readOnlyHint=true. The description adds significant behavioral context: the wiki-editing nature of setlists, the structure of response fields (sets, songs, attributes like tape, cover, with, info), and important attribution requirements (clickable url, no nofollow, fallback link).

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 description is longer but every sentence adds value: purpose, source of versionId, response field explanations, and attribution rules. It is front-loaded with the action, making it clear and purposeful.

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?

Given the single parameter, no output schema, and complex response structure, the description thoroughly covers what the agent needs to know: how to call the tool, interpret the result, and present it with proper attribution. No gaps are evident.

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?

The schema describes the `versionId` parameter as 'Setlist version ID' (100% coverage). The description adds valuable context by explaining that version IDs come from a setlist's `versionId` field, aiding the agent in obtaining the correct value.

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 a specific historical version of a setlist by its version ID. It uses a specific verb and resource, and distinguishes from siblings like `setlist_get_setlist` (current version) and search tools.

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 explains when to use the tool (to get a historical version via versionId) and how to obtain the versionId (from a setlist's `versionId` field). It does not explicitly mention when not to use it or name alternative tools, but the context is clear.

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