kpi_uninstalls

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

No annotations are provided, so the description carries the full burden. It implies a read operation and a time-series result, but says nothing about auth requirements, rate limits, data freshness, timezone handling, maximum ranges, or return format.

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?

A single front-loaded sentence with no wasted words. It is as concise as possible while still naming the operation and resource.

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 5-parameter analytics tool with no annotations, no output schema, and 60% schema description coverage, the one-line description is too thin. It omits required parameter semantics, return value expectations, and behavioral constraints an agent would need to call it correctly.

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 60%, with only apiKey and length described in the schema. The description adds no parameter meaning; 'over time' loosely hints at temporal parameters but does not explain app_id, ending_at, or how length interacts with the result.

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 verb ('Get') and resource ('app uninstalls over time'), which is clear enough to distinguish it from most siblings. However, it does not explicitly differentiate itself from other KPI tools like kpi_dau, kpi_mau, or kpi_new_users.

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 use this tool versus alternatives such as sessions_analytics or other KPI endpoints. The implied context is analytics, but no explicit when-to-use or exclusions are given.

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