OpenPanel: Get event count

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

readOnlyHint=true already tells the agent this is a safe read. Beyond that, the description only adds "via Export API," which faintly suggests a bulk/export path that may differ in latency or limits, but it never explains the return shape, aggregation semantics, or any rate/quota behavior. It does not contradict the annotations, but it adds limited behavioral context.

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?

One short, front-loaded sentence with no filler; the action and data source come first. The "[UNIFIED]" tag is unused noise, but the sentence itself is efficiently sized.

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 four-parameter tool with no output schema, zero schema description coverage, and only a readOnly annotation, the description is far too thin. It never explains what a "count" includes, the granularity of the result, or how the date_range and event filters interact.

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 0% for all four parameters, so the description must carry the load and does not: it says only "optional filters" without clarifying that site is required, that date_range defaults to 30d, or what event and project_id mean. The agent must guess at parameter syntax and semantics from names alone.

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 gives a specific verb and resource ("Get total event count") plus a data source ("via Export API"), so the agent knows what it returns. It does not differentiate from adjacent reporting siblings such as openpanel_get_unique_users or openpanel_get_page_views, and the "[UNIFIED]" prefix carries no decodable meaning.

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?

There is no guidance on when to choose this tool over the many sibling count/report tools, nor any stated prerequisites (e.g., which API tier or credentials are needed). "With optional filters" implies the parameters narrow results but never says what to filter on or when filtering is required.

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