list_past_classes

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only mentions navigation and listing, but does not explain side effects (e.g., changing current tab), return value, or whether login is required. This is a significant gap for a tool with no output schema.

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?

The description is a single, front-loaded sentence with no redundancy. However, 'Navigate to Past Classes tab' is an implementation detail that could be omitted for clarity, and the phrase 'list all past classes' could be more explicit about output.

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 and no annotations, the description is insufficiently complete. It does not state what the tool returns (if anything), whether it requires a browser or login, or how it differs from scrape_all_past_classes. For a simple tool with zero parameters, some gaps are acceptable, but this lacks essential context.

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?

The tool has zero parameters, so the baseline is 4. The description correctly avoids parameter details since there are none. No additional semantic value is needed.

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 clearly states the action ('list') and the resource ('past classes'), with a specific navigation step ('Navigate to Past Classes tab'). It distinguishes itself from sibling tools like list_courses (courses vs classes) and scrape_all_past_classes (scraping vs listing).

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 description implies its use case: listing past classes. However, it provides no explicit when-to-use versus alternatives, nor any exclusions or conditions. Given sibling tools like list_courses and scrape_all_past_classes, explicit differentiation would improve clarity.

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