list_courses

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds useful behavioral context: the result ordering (most recently visited first) and the meaning of hidden courses (ones you don't follow). It could mention more about pagination or response volume, but given the annotation coverage, it exceeds the baseline.

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 compact and front-loaded with the primary purpose, followed by one relevant contextual note and a concise Args section. No sentence is wasted, and the structure makes the two optional parameters easy to scan.

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 is simple with two optional booleans and an output schema already present. The description covers ordering, hidden-course semantics, and both parameters. Nothing needed to safely invoke this tool correctly is missing.

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 0%, so the description bears the full burden of explaining parameters. It does so clearly: include_past ('Also list courses whose end date has passed') and include_hidden ('Also list courses hidden on your dashboard'). Each boolean's effect is explicit, and the word 'Also' implies the default false behavior matching the schema defaults.

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 a specific verb ('List'), a clear resource ('courses you're enrolled in'), and a distinctive ordering ('most recently visited first'). It also distinguishes itself from siblings by explaining that hidden dashboard courses are skipped by other tools unless named explicitly, which helps disambiguate from course_overview and similar tools.

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 gives clear context about when this tool is relevant and explains hidden-course semantics relative to other tools ('other tools skip them unless you name them explicitly'). It does not explicitly name sibling alternatives or provide a direct when-to-use versus when-not-to-use comparison, but the context is strong enough for an agent to make a reasonable choice.

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