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

Annotations already cover readOnly, idempotent, destructive=false and openWorld, so the safety profile is established. The description adds the corpus scale and content composition, plus the auth requirement, but says nothing about pagination behavior or result volume on the corpus this size.

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 plus an example, front-loaded with the corpus scope before the filtering and auth details. The _apiKey mention is mild duplication of the schema field but reads as useful prompt-level emphasis rather than bloat.

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 no output schema, the description carries some return-value burden but only implies result shape via the cursor/limit fields in the schema; it never explains pagination or next_cursor use. For a read-only search tool with fully documented params and annotations, it is nearly complete but stops short on result handling.

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 all six parameters including limit, cursor and podcast slug are already documented at the schema level. The description's example adds a little usage syntax but no meaning beyond the schema, so the 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 (Search) and resource (CanonCannon episode corpus) with concrete scope: 10,000+ podcast episodes with extracted ideas, guests and books. An agent can distinguish it from canon_episode_get (single episode) and canon_podcast_list (show listing) without opening schemas.

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?

Clearly states the three filtering modes (show, publication date, free text) and includes a worked example, which tells the agent how to invoke it. However, it gives no explicit routing guidance against the ambiguous siblings canon_search and search_within, so when-not-to-use is left to inference.

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