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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds meaningful behavioral detail: the artist record includes nullable mbid and verified spotify_id, and each performance carries a ticket_url resolved to the closest-to-purchase link. This helps set expectations for the returned data.

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?

Three tight sentences: the first defines scope, the second gives concrete usage examples, and the third clarifies a key return field. Every sentence earns its place with no redundant material.

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?

The description covers main return fields and a realistic use case, but it leaves a meaningful gap: 0 parameters are required while the tool promises 'one artist', so an agent may be unsure whether name, slug, or artist_id must be supplied. With no output schema, this ambiguity is not resolved elsewhere.

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 the parameters are already well documented. The description adds no extra parameter semantics, such as which identifier is preferred or how filters combine, so it stays at the baseline 3.

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 names a specific verb and resource: 'List one artist's stable identity and performances with filtering and pagination.' It also gives a concrete example query. However, it does not explicitly differentiate this tool from siblings like search_events or get_artist, though the 'one artist's' scope is a good implicit cue.

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 provides clear use cases: answering 'Where is Peggy Gou playing in Europe next month?' and paging through a touring artist's full schedule. This tells an agent when to use the tool, but it does not mention exclusions or when to prefer an alternative such as search_events.

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