Coursera MCP Server

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

No annotations are provided, so the description carries full burden. It mentions what the tool returns (titles, providers, ratings, difficulty, URLs) but doesn't disclose important behavioral traits like whether this is a read-only operation, potential rate limits, authentication requirements, or pagination behavior. The description adds some value about return format but misses key operational context.

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 perfectly concise - two sentences that efficiently convey purpose and return format with zero wasted words. It's front-loaded with the core functionality and follows with output details, making it easy for an agent to quickly understand the tool's value.

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 search tool with 4 parameters and no output schema, the description provides adequate but incomplete context. It covers the purpose and return format but lacks behavioral transparency (no annotations) and doesn't explain result ordering, error conditions, or how the search algorithm works. The 100% schema coverage helps, but the description should do more given the absence of annotations and output schema.

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 doesn't add any meaningful parameter semantics beyond what's in the schema - it mentions search criteria but doesn't provide additional context about parameter usage, interactions, or examples not already covered in the schema descriptions.

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 specific action ('Search Coursera for courses'), the resource ('courses'), and the search criteria ('by topic, skill, or keyword'). It distinguishes itself from siblings like 'get_course_details' (specific course info) and 'get_my_courses' (user's enrolled courses) by focusing on broad search functionality.

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 usage for general course discovery but doesn't explicitly state when to use this tool versus alternatives. For example, it doesn't clarify whether to use 'search_courses' for initial discovery versus 'get_course_details' for detailed information on a specific course, or how it differs from 'get_my_courses' for enrolled courses.

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