scrape_all_past_classes

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

No annotations are provided, so the description must carry full weight for behavioral disclosure. It describes the main action (extract transcripts/resources) but fails to disclose side effects such as writing files to outputDir, potential overwrites, the need for prior login/track selection, or expected duration for a bulk operation. The 'bulk' nature hints at scale but does not elaborate on behavioral implications.

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?

A single, front-loaded sentence that efficiently communicates the tool's purpose without wordiness. Includes key qualifiers ('bulk', 'all past classes', 'current track') and specifics ('transcripts and resources'). No wasted words.

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?

The tool has only 2 optional params, no output schema, and no annotations. The description covers the core purpose and references the artifacts extracted, but omits operational context such as filesystem effects, prerequisites, cleanup behavior, and whether it returns a summary. Given the bulk nature, more context could be useful, but the minimal description is not severely inadequate.

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?

Both parameters have full descriptions in the input schema (100% coverage), so the baseline is 3. The tool description does not add extra parameter semantics beyond referencing 'transcripts and resources' which aligns with includeResources. No additional value is provided, but the schema already covers the details.

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 states the tool bulk scrapes all past classes in the current track, specifically extracting transcripts and resources. This is a specific verb+resource combination that clearly distinguishes it from sibling tools like list_past_classes (listing only) and extract_transcript/extract_resources (single-class operations).

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?

The phrase 'bulk scrape all past classes in the current track' clearly implies use when you need all past classes at once rather than individually. However, it does not explicitly contrast with alternatives or state prerequisites like having a track selected, so it lacks the explicit when/when-not guidance needed for a 5.

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