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. It states this is a GraphQL operation and clarifies parameter mapping ('content' for body, 'parentId' for post ID), but doesn't disclose critical behavioral traits like whether this is a mutation (likely yes), what permissions are required, if it's rate-limited, or what the response looks like. For a write operation with zero annotation coverage, this is insufficient.

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 brief and front-loaded with the core purpose. The note about parameter mapping is helpful but could be more integrated. No wasted sentences, though it could be slightly more structured for clarity.

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 this is a write operation (replying to a post) with no annotations and no output schema, the description is incomplete. It doesn't explain what happens after the reply (e.g., success response, error handling), permissions needed, or how it differs from other post tools. For a mutation tool in a GraphQL context, more behavioral context is warranted.

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 clearly documented in the schema. The description adds minimal value by clarifying that 'content' maps to 'body' and 'parentId' maps to 'postId', but this is redundant with the schema. Baseline 3 is appropriate since 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 ('Reply to a post') and the resource ('a post'), making the purpose immediately understandable. However, it doesn't distinguish this tool from other post-related siblings like 'gql_create_post' or 'gql_update_post' beyond the 'reply' action, which is why it doesn't reach 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 like 'gql_create_post' for new posts or 'gql_update_post' for editing. It mentions GraphQL context but doesn't explain why this specific tool is needed over non-GraphQL options, leaving usage context unclear.

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