list_courses

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 implies a read-only operation by saying 'Get a list', but does not state any prerequisites (e.g., login), whether the list is session-dependent, or the format/scope of the returned list. For a simple tool this is a notable gap.

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, directly stated sentence with no extra words or fluff. It is appropriately sized and fully front-loaded, stating the action and resource immediately.

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 very simple (no parameters, no output schema), so the description is arguably sufficient to understand what it does. However, it lacks information about return structure, prerequisites like authentication, or how it fits into the broader workflow. For such a minimal tool, this is adequate but with clear gaps.

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's properties are empty, so the description has no parameter burden. The description adds meaningful context about the source ('from the dashboard') and what is returned (available courses), which is more than sufficient given the lack of parameters.

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 a specific verb ('Get') and resource ('a list of available courses from the dashboard'), clearly distinguishing it from siblings like 'list_tracks' (tracks) and 'select_course' (selection). It is unambiguous and immediately actionable.

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?

No guidance on when to use this tool versus alternatives. It does not say whether to call it before selecting a course, if login is required, or how it relates to 'list_tracks' or 'select_course'. The only implied usage is that it lists courses, but no explicit context or exclusions are given.

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