list_courses

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

With no annotations provided, the description carries the burden of behavioral disclosure. It indicates a read-only operation by saying 'List', and it describes the return format (JSON array with specific fields). However, it does not mention any authentication requirements, pagination, sorting, or potential errors. The description is adequate but not rich in behavioral detail.

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 two sentences, front-loaded with the purpose, followed by a concise return value listing. Every sentence earns its place, and there is no redundant information.

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 simple tool with zero parameters and a clear output schema, the description provides sufficient information about what it does and what it returns. It does not mention edge cases (e.g., empty list, inactive courses), but given the simplicity, this is not a significant gap. It is complete for its intended use.

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 there is no parameter information required. The schema coverage is 100% trivially. The baseline for zero parameters is 4.

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 tool lists all courses where the current user is enrolled, using a specific verb ('List') and a specific resource ('courses'). It distinguishes from sibling tools like list_categories (categories) and get_course_contents (contents of a single course) by the scope of 'where the current user is enrolled'.

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 provides clear context for when to use the tool: when the current user wants to see their enrolled courses. It does not explicitly name alternatives or mention when not to use it, but the context is unambiguous. No exclusions are given.

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