Thinkific MCP Server

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

No annotations are provided, so the description carries the full burden. It states the action ('List coupons') but doesn't disclose behavioral traits like pagination behavior (implied by 'page' and 'limit' parameters but not explained), rate limits, authentication needs, or what the output looks like. For a read operation with no annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 with zero waste. The first sentence states the purpose, and the second adds essential context about the coupon-promotion relationship. It's front-loaded and efficiently structured, making it easy to parse.

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 moderate complexity (3 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the purpose and resource relationship but lacks details on behavior, output format, and usage guidelines. With no output schema, the description should ideally hint at return values, but it doesn't, leaving gaps for an agent to infer.

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%, with clear descriptions for all parameters (e.g., 'Promotion ID (use list_promotions to find IDs)'). The description adds minimal value beyond the schema, as it doesn't explain parameter interactions or provide additional context. With high schema coverage, the baseline is 3, and the description doesn't significantly enhance parameter understanding.

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 verb ('List') and resource ('coupons for a promotion'), and specifies the relationship to promotions ('Thinkific coupons belong to promotions'). It distinguishes from siblings like 'get_coupon' (singular) and 'bulk_create_coupons', but doesn't explicitly differentiate from other list tools like 'list_promotions'. The purpose is specific and actionable.

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 when needing coupons for a specific promotion, and the parameter description for 'promotion_id' references 'list_promotions' to find IDs, providing some contextual guidance. However, it lacks explicit when-to-use vs. alternatives (e.g., 'get_coupon' for a single coupon) or prerequisites. Usage is implied but not fully articulated.

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