list_tracks

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the operation (list) and scope (current course) but does not mention what happens if no course is selected, whether authentication is required, or what the return format includes. For a simple read-only list, this is adequate but not richly transparent.

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, concise sentence (8 words) that front-loads the verb and resource. Every word earns its place, with no fluff or redundancy, making it optimally concise and easy to parse.

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?

For a no-parameter, no-output-schema tool, the description is nearly complete: it states what the tool lists and the scope ('current course'). However, it does not explicitly describe the return value structure (e.g., track names, IDs), which could be helpful given the absence of an output schema. This is a minor gap, keeping it from a perfect score.

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?

There are zero parameters, and the schema is empty, so the description naturally has no parameter details to add. The baseline for no-parameter tools is 4, and the description adequately covers the tool's behavior without needing to compensate for missing parameter information.

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 uses the specific verb 'List' and identifies the resource as 'available tracks/modules within the current course'. This clearly distinguishes it from siblings like list_courses (courses vs tracks) and select_track (selection vs listing), leaving no ambiguity about its function.

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 'within the current course' provides clear context that a course must be selected before calling this tool. It does not explicitly mention alternatives or exclusions, but the context strongly implies its use for browsing tracks prior to selecting one, making the usage intuitive.

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