get_realtime_analytics_daywise

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does convey read-only intent via the verb 'Get' and a time grain via 'daily', but it does not reveal return shape, aggregation semantics, limits, or any special requirements beyond the schema.

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 concise and front-loaded, with zero wasted words. However, it is under-specified rather than efficiently complete; a few substantive details would earn their place and improve the definition.

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?

With no annotations and no output schema, the description must explain what the agent will get back and why this tool is the right one. A single vague phrase about daily analytics is insufficient for distinguishing it from the large set of realtime and analytics siblings.

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 100% and both required parameters are already documented in the schema. The description adds no additional meaning about how account_id and app_id relate to the returned analytics, so the baseline 3 is appropriate.

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 essentially restates the tool name: 'Get Realtime Kit daily analytics' is 'get_realtime_analytics_daywise' with 'Kit' inserted. It does not clarify what Realtime Kit is, what metrics are included, or how this differs from the many realtime and analytics sibling tools.

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 about when to use this tool versus alternatives such as get_zone_analytics, get_analytics_by_colo, graphql_analytics, or the get_realtime_* summary tools. No prerequisites or context scenarios are provided.

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