Mixpanel MCP Server

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool runs scripts but doesn't cover critical aspects like authentication needs, rate limits, execution time, error handling, or data modification risks (e.g., whether it's read-only or can mutate data). This leaves significant gaps for safe and effective use.

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 two sentences with zero waste: it directly states the tool's function and key capability. It's front-loaded and appropriately sized, making it easy to parse without unnecessary details.

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 complexity of running custom scripts against data, lack of annotations, and no output schema, the description is incomplete. It doesn't address behavioral risks, return values, or integration with sibling tools, leaving the agent under-informed for a potentially powerful operation.

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 the schema already documents both parameters (script and params). The description adds minimal value by implying 'complex custom queries' but doesn't elaborate on parameter usage, syntax, or examples beyond what the schema provides, meeting the baseline for high coverage.

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 ('Run a JQL script') and target ('against Mixpanel data'), with specificity about the query language. It distinguishes from siblings by mentioning 'complex custom queries,' which suggests capabilities beyond simpler query tools like query_events or query_funnels, though not explicitly named.

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 query_events or export_events. It mentions 'complex custom queries' but doesn't specify scenarios or prerequisites, leaving the agent to infer usage without explicit direction.

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