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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It does add useful context by mentioning that each performance includes ticket_url (the resolved closest-to-purchase link) and the raw source page URL, which hints at the return structure. However, it omits critical behavioral facts: it does not mention that an artist identifier (name, slug, or artist_id) is required despite the schema listing all parameters as optional, nor does it explain default behaviors like upcoming_only=true. These are significant oversights for a tool with zero annotation support.

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 three sentences with no wasted words. It front-loads the primary purpose, then provides a concrete example, and ends with a valuable detail about the return data (ticket_url). Each sentence adds essential information without redundancy, making it efficient and well-structured.

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?

While the description includes an example and a return data hint, it fails to specify that an artist identifier is effectively required even though all schemas are optional. Without that explicit guidance, an agent might call the tool without any filter and get unexpected results. Additionally, there is no output schema, so the description should outline the standard fields or note pagination behavior more explicitly. These gaps prevent it from being fully complete.

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 every parameter already has a description. The tool description adds only general context about filtering and pagination, which does not go beyond what the schema provides. Since the description does not elaborate on parameter formats, interdependencies, or selection criteria, the baseline of 3 is appropriate.

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's function: 'List one artist's performances with filtering and pagination.' It uses a specific verb and resource, and provides a concrete example ('Where is Peggy Gou playing in Europe next month?') that distinguishes it from broader search tools. The scope is unambiguous and immediately separates it from sibling tools like search_events which cover multiple artists.

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 gives explicit usage examples ('answer this question' or 'page through a touring artist's full schedule'), which strongly implies when to use it. However, it does not mention alternatives or explicitly state when not to use it, such as for cross-artist searches. This is a minor gap since the examples clarify the intended use case.

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