Thinkific MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'with pagination', which is useful context about the return format, but doesn't describe other important behaviors like whether this is a read-only operation, what authentication is required, rate limits, or what the response structure looks like. For a list tool with zero annotation coverage, this leaves significant gaps.

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 - a single sentence that communicates the core functionality and key behavioral trait (pagination) with zero wasted words. It's front-loaded with the essential information and doesn't contain any unnecessary details.

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 list tool with 2 well-documented parameters and no output schema, the description is minimally adequate. It covers the basic purpose and mentions pagination, but lacks important context about authentication requirements, response format, and when to use versus other list tools. The absence of annotations means the description should do more heavy lifting than it does.

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 description doesn't add any parameter semantics beyond what's already in the schema, which has 100% coverage with clear descriptions for both 'page' and 'limit'. The baseline score of 3 is appropriate since the schema does the heavy lifting, though the description could have explained the pagination behavior more explicitly.

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 ('List') and resource ('courses on the Thinkific site'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'list_bundles' or 'list_categories', which would require mentioning it specifically lists courses rather than other entities.

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 no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when to choose this over other list tools (e.g., 'list_bundles'), or any contextual constraints. The agent must infer usage from the tool name alone.

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