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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered by structured data. The description usefully adds what content is returned and that catalog enumeration is out of scope, but says nothing about pagination, the limit cap, or how date ranges affect the returned events.

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, zero filler, and the use-condition and scope caveat are front-loaded ahead of the argument syntax. Nothing is redundant or buried.

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?

With six parameters split across two invocation modes, no output schema, and a 'limit' that caps at 20, the description leaves the filter behavior (city, date_from, date_to, limit) unexplained. Annotations cover safety, but an agent still lacks enough to know how the optional filters shape the response.

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 only 33%: id and query are documented, while city, limit, date_from, and date_to are documented nowhere. The description repeats the id/query duality already encoded by the schema's anyOf but adds no meaning for the four undocumented filters, which are exactly the parameters tied to its advertised 'upcoming events' payload.

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+resource and enumerates the payload (profile, graph context, published links, upcoming events), which is more than a restatement of the name. However, it never distinguishes itself from near-identical siblings like get_artist_page and get_artist_events, and 'upcoming events' actively overlaps with the latter, so an agent may struggle to route between them.

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?

It opens with an explicit when-to-use condition ('Use this when a user wants...') and adds invocation guidance ('Pass an id or a name query') plus a negative scope statement ('does not enumerate the artist catalog'). It stops short of naming any alternative sibling for the overlapping lookups, so it is clear context without full exclusion routing.

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