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

The description states the tool uses a GET request, consistent with the readOnlyHint annotation. Annotations already declare readOnlyHint=true, so the burden is lower. The description adds no further behavioral notes (e.g., rate limits, pagination, or default values), but the combination of annotations and schema covers basic behavioral 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 extremely concise: one sentence plus a short API note. Every piece of information is essential, and it is front-loaded with the primary action. No wasted words.

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?

The tool has 8 parameters (3 required) and no output schema. The description does not explain the return format or typical response, which could be important for an agent. While the high schema coverage partially compensates, the lack of output behavior is a gap. Still, the description provides enough context for basic usage.

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?

With 100% schema description coverage, the input schema already documents all 8 parameters. The description adds value by indicating that funnel_id comes from mixpanel_list_funnels, but does not elaborate on other parameters beyond what the schema provides. Baseline 3 is appropriate given 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 explicitly states the tool 'Get conversion data for a saved funnel', linking it to a specific resource (saved funnel) and verb (get conversion data). It also references the sibling tool mixpanel_list_funnels to find the funnel_id, clearly distinguishing its purpose from other Mixpanel tools like mixpanel_segmentation or mixpanel_retention.

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 a clear prerequisite: use mixpanel_list_funnels to obtain the funnel_id. It also mentions the underlying API call (GET /funnels). While it does not explicitly list when not to use or name alternatives, the context of sibling tools and the specific reference to list_funnels gives sufficient guidance.

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