openpanel_get_usage_stats

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions including events and users but fails to clarify if this is real-time vs historical, aggregated vs raw data, or safe read-only behavior. The '[UNIFIED]' prefix is unexplained.

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?

Single sentence is appropriately brief, but '[UNIFIED]' tag adds unexplained metadata and 'etc.' is vague filler. Structure is front-loaded but underspecified.

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 3 parameters with no schema descriptions, no annotations, and no output schema, the description should comprehensively document parameters and expected return format. It provides only a high-level purpose statement, leaving significant 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?

Critical failure: schema has 0% description coverage for all 3 parameters, yet the description provides zero semantic context for site, project_id, or date_range (e.g., format of '30d', relationship between site and project_id).

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?

States specific verb (Get) + resource (usage statistics) and mentions scope (events, users). However, it fails to clearly distinguish from sibling tools like openpanel_get_project_stats or openpanel_get_realtime_stats, which appear to serve similar analytics purposes.

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 guidance provided on when to use this tool versus alternatives such as openpanel_get_project_stats, openpanel_get_realtime_stats, or openpanel_get_event_count. No mention of prerequisites or filtering capabilities.

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