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 of behavioral disclosure. It states 'List instructors' but doesn't mention that it's a read-only operation, requires pagination (implied by schema but not described), or any rate limits or authentication requirements. For a tool with zero annotation coverage, this leaves significant gaps in understanding its behavior and constraints.

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: 'List instructors on the Thinkific site.' It is front-loaded with the core purpose, has zero wasted words, and appropriately sized for a simple list operation. Every word earns its place without under-specification.

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 (simple list with pagination), lack of annotations, and no output schema, the description is incomplete. It doesn't cover behavioral aspects like read-only nature, authentication needs, or response format. For a tool with 2 parameters and no structured safety hints, more context is needed to ensure the agent can use it correctly.

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 schema description coverage is 100%, with clear documentation for 'page' and 'limit' parameters including defaults and constraints. The description adds no additional parameter semantics beyond what the schema provides, such as explaining the pagination model or result ordering. Baseline 3 is appropriate when the schema does the heavy lifting, but no extra value is added.

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 'List instructors on the Thinkific site' clearly states the verb ('List') and resource ('instructors'), specifying what the tool does. It distinguishes itself from sibling tools like 'get_instructor' (singular retrieval) and 'create_instructor'/'delete_instructor'/'update_instructor' (mutations). However, it doesn't explicitly mention pagination or filtering capabilities, which slightly reduces specificity.

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 retrieving multiple instructors, contrasting with 'get_instructor' for single retrieval. However, it lacks explicit guidance on when to use this tool versus alternatives like 'list_users' or 'search_users' for broader queries, or prerequisites such as authentication needs. The context is clear but incomplete for optimal agent decision-making.

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