Clamp Analytics MCP Server

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

With no annotations provided, the description carries full burden. It discloses key behaviors: the funnel is 'saved for later retrieval' (persistence), 'immediately evaluate' (execution timing), and 'Requires Pro plan' (access control). However, it doesn't mention rate limits, error conditions, or what happens if steps are invalid.

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 efficiently structured with four sentences that each add value: purpose, what a funnel does, step format examples, and plan requirement. No wasted words, and key information is front-loaded.

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 2-parameter creation tool with no annotations and no output schema, the description covers purpose, usage context, and behavioral aspects well. However, it doesn't describe the return format ('Returns step-by-step counts...' but no details on structure) or potential limitations, leaving some 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%, providing comprehensive parameter documentation. The description adds minimal value beyond the schema, only reinforcing that steps can be event names or pageviews with paths. Baseline 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 tool's purpose with specific verbs ('create and immediately evaluate a conversion funnel') and resources ('tracks unique visitors completing a sequence of steps'). It distinguishes from siblings by focusing on funnel creation/evaluation rather than retrieval (get_funnel) or other analytics functions.

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 clear context about when to use this tool ('create and immediately evaluate a conversion funnel') and mentions a prerequisite ('Requires Pro plan'). However, it doesn't explicitly contrast with alternatives like get_funnel or specify when not to use it.

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