Coursera MCP Server

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 adds useful context about authentication requirements (environment variables or direct parameters), which is critical for a mutation tool. However, it lacks details on potential side effects (e.g., enrollment confirmation, payment requirements, or error handling), leaving behavioral traits partially covered.

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 appropriately sized with two sentences that efficiently convey key information: the core action and authentication details. It's front-loaded with the main purpose, and each sentence adds value without redundancy, though it could be slightly more structured (e.g., separating authentication notes).

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 the tool's complexity as a mutation tool with no annotations and no output schema, the description is moderately complete. It covers authentication needs but misses details like what happens on success/failure, whether enrollment is immediate or requires confirmation, and any rate limits. For a tool that modifies state, more behavioral context would improve completeness.

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 documents all parameters thoroughly. The description adds minimal value beyond the schema by mentioning authentication context, but it doesn't provide additional semantic details about parameters like format examples for 'course_url' or security considerations for 'password'. Baseline 3 is appropriate when the schema does the heavy lifting.

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 action ('Enroll in') and resource ('a Coursera course'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_my_courses' or 'search_courses', but the enrollment action is distinct enough from read-only operations.

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 some usage context by mentioning authentication requirements and environment variable alternatives, which helps understand when authentication is needed. However, it doesn't explicitly state when to use this tool versus alternatives like 'get_course_details' for checking course information before enrolling, leaving usage guidance implied rather than explicit.

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