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 but only states it's a list operation with filtering. It doesn't disclose pagination behavior (implied by page/limit parameters but not explained), rate limits, authentication requirements, or what happens when no filters are applied. The description is minimal and lacks behavioral context beyond the basic operation.

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 a single, efficient sentence with zero wasted words. It's front-loaded with the core purpose and includes the key filtering capability. Every word earns its place.

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 list tool with 5 parameters, 100% schema coverage, but no annotations and no output schema, the description is inadequate. It doesn't explain the return format, pagination behavior, error conditions, or how filtering interacts with pagination. The agent would need to infer too much from the parameter names alone.

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 all parameters are documented in the schema. The description adds marginal value by mentioning filtering by user or course, which aligns with query_user_id and query_course_id parameters, but doesn't provide additional context beyond what's in the schema descriptions. Baseline 3 is appropriate when 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 verb ('List') and resource ('enrollments') with optional filtering capabilities. It distinguishes this tool from other list_* tools by specifying the enrollment resource type, though it doesn't explicitly differentiate from 'list_bundle_enrollments' among the siblings.

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 like 'get_enrollment' (for single enrollment) or 'list_bundle_enrollments'. It mentions filtering options but doesn't explain when filtering is appropriate or what happens without filters.

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