openpanel_get_storage_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. While it mentions ClickHouse as the storage backend, it lacks critical information about read-only safety, rate limits, error handling for invalid site/project_id combinations, or response structure.

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 brief (single sentence), but the '[UNIFIED]' prefix appears to be internal metadata noise rather than helpful context. While efficiently sized, it is too minimal given the lack of schema documentation and annotations.

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 zero schema description coverage, no annotations, and no output schema, the description is insufficiently complete. It should elaborate on parameter semantics, return value structure, and behavioral characteristics to compensate for the missing structured metadata.

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?

The input schema has 0% description coverage for both required parameters ('site' and 'project_id'). The description completely fails to compensate by explaining what these parameters represent, their expected formats, or how to obtain valid values, leaving the agent blind to required inputs.

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 clearly states the tool retrieves 'storage usage statistics' and specifies the data source as 'events stored in ClickHouse', providing specific verb and resource identification. However, it fails to differentiate from similar sibling tools like 'openpanel_get_usage_stats' or 'openpanel_get_project_stats'.

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 is provided on when to use this tool versus alternatives. Given the presence of similar statistics tools in the OpenPanel suite (usage_stats, project_stats), the absence of selection criteria or prerequisites leaves the agent without decision-making support.

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