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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world fetching are covered. The description usefully adds that results are a current snapshot of both live and upcoming shows and lists the returned attributes, but says nothing about pagination, result limits, or empty-league behavior.

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?

One sentence, front-loaded with the action and scope, then the returned fields. No filler or repetition; it could add a sentence of routing guidance without bloat, but as written it is tight.

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?

An output schema exists, so field enumeration is not strictly required and annotations cover the read-only profile. However, for a one-parameter tool the missing league format and lack of routing to fanaticslive_leagues leave a real gap an agent must guess through.

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 coverage is 0% and the single 'league' parameter is undocumented in both schema and description. The description implies league is a filter, but does not clarify whether the value is a name, slug, or numeric ID, which is the key ambiguity for invocation; still, the implied filtering role gives some meaning.

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?

States a specific verb and resource ('live and upcoming shows') and the scoping filter ('under a league'), plus the fields returned. It is clear enough to distinguish from fanaticslive_show (single show) and fanaticslive_shop_shows, though it does not name those siblings as alternatives.

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?

There is no when-to-use guidance, no prerequisite stating that a league identifier must first be obtained from fanaticslive_leagues, and no exclusions relative to fanaticslive_live or fanaticslive_shop_shows. Usage must be inferred entirely from the name and the 'under a league' phrasing.

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