list_tracks

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

No annotations exist, so the description carries the full behavioral burden; it does add useful structure by explaining that exam objectives become subtopics, and read-only listing is strongly implied. It does not state that the call is non-mutating, whether results are user-personalized or filtered (e.g. already-started tracks excluded), or what pagination/limits apply.

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 short sentence with no waste and the scoping qualifier placed immediately after the resource. It reads as a label rather than a complete definition, so it under-specifies slightly rather than over-explaining.

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 should say more about what a returned track looks like and whether previously started tracks are included. The subtopic note partially compensates, but an agent still cannot predict the response shape.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. The description correctly implies no input is required.

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?

Names the resource precisely (certification/learning tracks) and scopes it to those 'the user can start', which separates it from in-progress track tools like get_progress. However, it is a noun fragment with no verb, so the fact that it enumerates rather than mutates is only implied.

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 'the user can start' hints that this is the discovery step preceding start_track, but no alternative is named and no when/when-not condition is stated explicitly. Usage must be inferred from the sibling list.

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