list_courses

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

With no annotations, the description carries the burden of behavioral disclosure. It does disclose the core behavior: it lists all courses for the current user and supports optional filters. However, it does not mention pagination behavior, response shape, whether deleted courses can appear, or any authentication or permissions expectations.

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, efficient sentence that front-loads the primary function before mentioning optional filters. There is no redundant wording or unnecessary qualification.

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 description adequately covers the basic list-and-filter use case, but it omits any reference to sibling tools like search_courses for broader course discovery, and it does not clarify returned data structure or pagination. Given there is no output schema, a bit more context about what the response contains would make it more complete.

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 description coverage is 100%, so the schema already fully documents all three parameters. The description simply restates that filtering by enrollment type and course state is possible, adding no semantic detail beyond what the schema provides.

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 a specific action ('List all courses') and a well-defined scope ('for the current user'), with optional filtering by enrollment type and course state. It distinguishes itself from single-course tools like get_course, though it does not explicitly contrast with search_courses.

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 implies when to use this tool: when the user needs their own courses and may want to filter them. However, it gives no explicit guidance about alternatives such as search_courses, get_course, or list_enrollments, and does not state when not to use it.

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