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 states the action is a 'bulk add' which implies a write/mutation operation, but doesn't specify permissions required, whether it's idempotent, error handling for partial failures, rate limits, or what the response looks like. For a mutation tool with zero annotation coverage, this leaves critical behavioral aspects undocumented.

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 action and includes the GraphQL implementation detail. Every word earns its place, making it highly concise while still conveying essential information.

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 mutation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens on success/failure, return values, error conditions, or system impacts. The 100% schema coverage helps with inputs, but the overall context for using this tool remains incomplete, especially given its potentially destructive nature.

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 both parameters ('userIds' and 'groupIds') clearly documented in the schema. The description adds no additional parameter semantics beyond what the schema provides—it doesn't explain format expectations, constraints, or relationships between the arrays. Baseline score of 3 is appropriate when the 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 action ('bulk add'), the target resources ('multiple users to multiple groups'), and the implementation method ('GraphQL'). It distinguishes from the simpler 'add_user_to_group' sibling tool by emphasizing bulk operations. However, it doesn't specify what 'bulk' means quantitatively or how it differs from other bulk operations like 'bulk_create_coupons'.

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 'add_user_to_group' for single operations or other bulk tools. It doesn't mention prerequisites, constraints, or typical use cases. The only implied context is the need for bulk operations, but this is minimal guidance.

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