MCP Hub

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

No annotations are provided, so the description must carry full behavioral disclosure. It fails to indicate whether this is a read-only operation (though implied), output format, rate limits, or what happens when project_id is omitted without environment configuration. Only the basic action is described.

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?

Extremely efficient at two sentences with zero redundancy. The constraint about project_id is placed immediately where relevant. Every word earns its place despite the minimal length.

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 7 parameters (including complex nested arrays), zero schema descriptions, no annotations, and no output schema, this tool requires substantial documentation. The two-sentence description is inadequate for an agent to correctly construct valid 'events' arrays or understand the aggregation behavior.

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 0% schema description coverage, the description must compensate for 7 undocumented parameters. It only addresses project_id's optionality. Critical required parameters 'site' and 'events' (an array of objects with unspecified structure) are completely unexplained, as are 'breakdowns', 'previous', and date filtering behavior.

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 states a specific action (Export) and resource (aggregated chart data) with key features (time series, breakdowns). The '[UNIFIED]' prefix is noise but harmless. It implicitly distinguishes from sibling 'export_events' and 'export_profile_data' tools by specifying 'chart data', though it lacks explicit differentiation guidance.

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 one concrete usage note: 'project_id is optional if configured in environment.' However, it lacks explicit guidance on when to use this versus sibling export tools (openpanel_export_events, openpanel_export_profile_data) or what constitutes valid 'events' input.

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