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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds meaningful context about sync states, the meaning of historyHorizonAt, and the reconnect behavior. It could have explicitly stated it makes no changes, but the annotation covers that.

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 slightly verbose and repeats some field names, but it packs essential usage guidance, status meanings, and a caveat about reconnects into a compact monologue. It is not bloated or redundant enough to hurt clarity.

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?

The description fully explains the return semantics, the statuses, the meaning of the history horizon, and the reconnect flow, along with actionable advice for the agent. It leaves no critical operational detail unexplained.

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?

There are no parameters, and the description explicitly states 'Takes no arguments.' The schema coverage is complete, so there is no ambiguity.

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 reports analytics sync freshness per connected account, which distinguishes it from analytics overview, timeseries, and platform breakdown siblings. It explicitly enumerates the returned status fields and their meaning.

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?

The description gives explicit guidance on when to call this tool: when numbers look stale or empty, and after trigger_analytics_sync to observe the run finish. It also tells the agent not to keep querying if needsAnalyticsReconnect is true.

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