Thinkific 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 for behavioral disclosure. 'List course categories' implies a read-only operation but doesn't specify pagination behavior (implied by parameters), authentication requirements, rate limits, or what happens when no categories exist. For a tool with zero annotation coverage, this is insufficient behavioral 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 a single, efficient sentence with zero wasted words. It's appropriately sized for a simple list operation and front-loads the essential information immediately.

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 100% schema coverage but no annotations or output schema, the description is minimally adequate. It identifies the resource but lacks behavioral context (pagination, auth, error cases) that would be helpful given the absence of structured metadata. The completeness is borderline acceptable but has clear gaps.

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 parameters 'page' and 'limit' are fully documented in the schema. The description adds no additional parameter semantics beyond what the schema already provides, which meets the baseline expectation 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 'List course categories' clearly states the verb ('List') and resource ('course categories'), making the purpose immediately understandable. However, it doesn't differentiate from similar sibling tools like 'get_category' (singular retrieval) or 'gql_category' (GraphQL alternative), which would require explicit comparison for a perfect score.

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. With sibling tools like 'get_category' (retrieves a single category) and 'gql_category' (GraphQL-based query), the agent receives no help in choosing between list vs. get operations or REST vs. GraphQL approaches.

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