list-courses

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

The description discloses the core behavior (listing courses) but lacks additional context such as read-only nature, authentication requirements, or performance characteristics. Since no annotations are provided, the description carries full burden and could be more informative.

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 concise sentences, front-loaded with the action. Every sentence earns its place with no wasted words.

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?

Given no parameters and a simple purpose, the description is sufficient. It covers the what and when. Could optionally mention the return format, but not critical for this straightforward tool.

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 0 parameters, so baseline is 4. The description does not need to add parameter details, and it correctly omits any parameter-related 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 starts with 'List the courses the user is currently taking,' which is a specific verb and resource. It clearly distinguishes from siblings (list-course-files, search-course-file) by focusing on courses rather than files.

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?

States 'Agents should use this MCP tool whenever they need to check which courses are available,' providing explicit guidance on when to use. No exclusion criteria or alternatives are mentioned, but siblings are clearly different.

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