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

The description discloses all relevant side effects: it queues accounts, runs in the background, returns a queued status with cooldown info, and explicitly states it changes no content. It also details the cooldown semantics and that repeated calls within the cooldown do not queue again, making the tool's behavior fully transparent. No contradiction with annotations.

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 front-loaded with the primary purpose, then provides important usage and behavior details in a logical order. Though it is a single paragraph, every sentence contributes critical information without fluff or redundancy. Length is appropriate for the complexity.

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 tool with no input parameters and a likely simple output, the description gives sufficient context: it mentions the output fields (queued and cooldownSecondsRemaining), explains the background execution, and guides follow-up via get_analytics_sync_status. An agent can confidently invoke this tool based solely on this description.

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 zero parameters, so the description need not explain any. It explicitly states 'Takes no arguments,' which is clear and sufficient. Baseline for 0 params is 4, and the description adds no unnecessary detail, so it remains at that score.

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's purpose: to refresh analytics immediately rather than waiting for the scheduled sync. It explicitly describes what happens (every connected account is queued, last 7 days re-read) and contrasts it with the scheduled sync and get_analytics_overview, making its distinctive function obvious.

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?

Provides specific, actionable guidance: use it after publishing or when get_analytics_overview shows a stale lastSyncedAt. It also explains the cooldown behavior and instructs not to retry in a loop, and tells the agent to poll get_analytics_sync_status for completion. This is exemplary usage direction.

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