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

No annotations are provided, so the description carries the transparency burden. It discloses the ordering behavior ('Ordered by how many performances we track') and optional scoping, which adds value. It does not mention pagination, limits, or error behavior, but these are visible in the schema and are typical for a read-only list operation.

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 efficient: two sentences with a clear verb + resource + key behaviors, plus example questions. No wasted words; it front-loads the most important 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 list tool with 8 optional parameters, the description provides a solid high-level overview and use cases, but does not explain how parameters interact (e.g., upcoming_only default behavior with city/country). The schema covers the specifics, and the output schema is absent, so the description is reasonably complete for a browse operation.

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 baseline is 3. The description adds no parameter-specific semantics beyond the schema; it references city/country but does not explain parameters like query, source, min_events, or upcoming_only. The schema already documents these, so no deduction is warranted.

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 browses artists with optional city/country scoping, uses a specific verb and resource, and differentiates from siblings via its 'browse' positioning and ordering by tracked performance count. The example queries reinforce its purpose.

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 clear use cases with example questions ('Who is playing in Berlin this month?' or 'Which artists tour most?'), which imply when to use this tool. However, it does not explicitly mention alternatives or when not to use it (e.g., exact artist lookup via get_artist or full-text search via search_artists).

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