Read full WWDC session transcript in chunks

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

Annotations already establish read-only, idempotent, non-destructive, closed-world semantics, so the lower bar applies. The description adds genuinely useful behavioral context: the transcript arrives in bounded chunks and iteration terminates at totalChunks, which is not encoded in the annotations.

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?

Three short sentences, zero filler, with the core purpose and the paging loop front-loaded and the alternative-tool note last. Every sentence carries distinct 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?

No output schema exists, but the description implies the response includes a totalChunks field and usable text chunks, and it covers the paging loop an agent must drive. A brief note on what each chunk contains or the format trade-off would make it fully self-sufficient.

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 100%, so the baseline is 3. The description goes beyond the schema by explaining how chunk_index is driven (start at 0, increment, compare against totalChunks), turning an isolated parameter into a paging protocol an agent can execute.

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 ('Retrieve the complete transcript of a WWDC session') plus the delivery mechanism ('in paginated chunks'). It also contrasts itself against the sibling wwdc_get_session by framing itself as the full-transcript option versus that tool's excerpt.

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?

Gives an explicit usage protocol ('Use chunk_index=0 to start, then increment until chunk_index >= totalChunks') and a clear condition selecting this tool over wwdc_get_session. It stops short of stating exclusions (e.g. when to prefer wwdc_transcript_search for targeted lookups).

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