mixpanel_get_funnels

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the tool gets data, implying a read operation, but does not disclose any behavioral traits such as rate limits, data volume, required permissions, or whether the response includes step-by-step conversion counts or aggregated metrics.

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, concise sentence with no unnecessary words. It is front-loaded with the action and resource, which is optimal for quick comprehension.

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 has 7 parameters, no output schema, and no annotations, the description is insufficient. It neither explains what funnel conversion data comprises (e.g., steps, conversion rates) nor clarifies the time range implications (from_date, to_date, unit). The agent must infer critical details from parameter names alone.

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 coverage is 100%, so the schema already documents all 7 parameters with descriptions. The tool description adds no additional meaning beyond the schema, such as how to construct effective queries or parameter interactions. 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 'Get funnel conversion data from Mixpanel' clearly states the verb (get), resource (funnel conversion data), and source (Mixpanel). The resource name distinguishes it from sibling tools like mixpanel_get_events or mixpanel_get_retention, though it does not explicitly differentiate by scope (e.g., specific funnel vs. all funnels).

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?

No usage guidelines are provided. There is no indication of when to use this tool over alternatives (e.g., mixpanel_get_events), no prerequisites (e.g., need a funnel ID from Mixpanel UI), and no exclusions or context about data availability.

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