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. 'Refund' implies a financial mutation, but the description doesn't state whether this requires specific permissions, if it's reversible, what happens to the order status, or any rate limits or side effects. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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: 'Refund an external order.' It's front-loaded with the core action and resource, with no wasted words. However, it could be more structured by including brief usage notes, but as-is, it's concise and to the point.

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 (a financial mutation with 2 parameters), lack of annotations, and no output schema, the description is incomplete. It doesn't explain return values, error conditions, or behavioral nuances like partial vs. full refunds. For a refund operation, more context is needed to ensure safe and correct usage by an agent.

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 input schema has 100% description coverage, with clear parameter documentation: 'order_id' as the external order ID to refund and 'amount_cents' as the optional refund amount in cents. The description adds no additional semantic context beyond what the schema provides, such as examples or edge cases. With high schema coverage, the baseline score of 3 is appropriate.

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 'Refund an external order' clearly states the action (refund) and target resource (external order), which is adequate. However, it doesn't differentiate from potential siblings like 'purchase_external_order' or 'get_order', nor does it specify what makes an order 'external' versus internal. The purpose is understandable but lacks specificity about scope or differentiation.

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. It doesn't mention prerequisites (e.g., order must exist, be refundable), exclusions (e.g., cannot refund already refunded orders), or related tools like 'purchase_external_order' or 'get_order' for verification. Without such context, an agent might misuse it or overlook necessary checks.

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