Get account analytics

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and freshness are covered structurally. The description adds nothing about cost, rate limits, data freshness, or whether results are cached, which matter for a live-analytics read.

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 short sentence with no padding, which is appropriate in size, but it is under-specified rather than efficient—brevity here costs the agent information it needs.

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 and no documented parameters, the description is the only place an agent could learn the return shape and window semantics, and it supplies neither. For an analytics tool with a required ID plus an optional window it is too thin.

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% for both parameters. The phrase 'over a window' gestures at windowDays but gives no units, default, maximum, or allowed range, and accountId format is unexplained, so the description fails to compensate for the empty schema.

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?

Names the resource (an account's engagement summary) and its scope (a time window), but it is a noun phrase with no verb and 'engagement summary' is left undefined, so the agent cannot tell whether this returns counts, rates, or a fixed report. It does weakly differentiate from get_post_analytics by operating at the account level.

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 statement of when to call this versus get_analytics_summary, get_usage, get_post_analytics, or get_best_times, all of which sit nearby and look overlapping. The agent must infer the choice from names alone.

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