Get analytics summary

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

The annotations already declare this is a read-only, non-destructive, open-world operation, so the safety profile is covered. The description adds useful scope detail — only the LATEST row per account, limited to accounts the caller can access, bounded by the window — but says nothing about whether the data is cached versus freshly fetched (relevant given refresh_analytics exists) or how results are shaped.

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 sentence, front-loaded with the key scope constraint and free of padding. It is efficient, though the terseness borders on under-specification rather than optimal concision.

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 output schema, an optional undocumented parameter, and a crowded sibling space, the description should explain what a row contains and whether refreshes are needed. It omits all of that, leaving the agent to guess at the return shape and the default window.

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% and the single parameter windowDays has no schema description. The phrase 'in the window' gestures at it but does not state units, default behavior when omitted (it is optional), or any upper bound, so the description does not compensate for the documentation gap.

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 names the resource (analytics rows) and a scope (latest row per accessible account within a window), which is more specific than the title alone. But it has no verb and does not distinguish itself from close siblings such as get_account_analytics, get_bulk_post_analytics, and get_usage, so an agent cannot confidently pick it over those.

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 statement of when to use this tool, when not to, or which sibling it replaces. With four other analytics-related tools in the list (get_post_analytics, get_account_analytics, get_bulk_post_analytics, refresh_analytics), the absence of routing guidance is a real gap.

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