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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds the domain rule that a show must reach ceil(5%) of this roster to clear the canon bar, plus the auth requirement, but does not discuss pagination behavior or result shape. With annotations carrying the operational traits, a 3 is appropriate.

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 information-dense sentence plus a short example, with the core purpose front-loaded. The canon-bar parenthetical is long but earns its place by defining the returned roster's meaning.

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 read-only list tool with full schema coverage and no output schema, the description covers purpose, domain meaning, auth and an example. Pagination return values are left entirely to the cursor parameter description, which is an acceptable but minor gap.

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 limit, cursor and _apiKey are all documented in the schema. The description adds only an example call with limit: 100 and does not explain cursor usage or paging semantics beyond what the schema already says. Baseline 3 applies.

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+resource: it lists every podcast CanonCannon tracks, with episode count. The canon-bar framing ('denominator of the canon bar') tells the agent exactly what the returned set represents. It does not explicitly name canon_podcast_get as the single-item alternative, so sibling differentiation is only implicit.

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?

Usage is implied by the purpose ('the roster that forms the denominator') but there is no explicit guidance on when to call this versus canon_podcast_get, canon_search, or canon_corpus_stats. No exclusions or prerequisites beyond the API key are stated.

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