Refresh analytics

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

With no annotations, the description carries the behavioral burden. It usefully discloses that the operation is asynchronous and returns a job id, but it does not mention side effects, permissions, whether it overwrites existing analytics, or how to later retrieve the job result.

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 sentence delivers the core operation, target resources, async nature, and return behavior with zero filler. Every element earns its place.

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 tool has four undocumented optional parameters)Skip no output schema and no annotations, so the description must compensate for these gaps. It clarifies the high-level purpose but leaves critical invocation details unresolved, especially parameter semantics and whether postId or accountId is required.

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 description only hints that postId and accountId correspond to 'post or account'. The limit and windowDays parameters are not explained, and there is no guidance on which parameter combination is expected or whether one of postId/accountId is required.

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 states a specific verb ('Enqueue'), a clear resource ('analytics backfill'), and the valid targets ('a post or account'). It also notes that a job id is returned, which distinguishes this async operation from synchronous analytics-fetch siblings like get_post_analytics and get_account_analytics.

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 implies the tool is used when an asynchronous analytics backfill is needed, but it does not explicitly explain when to prefer this over get_post_analytics, get_account_analytics, or refresh_account. No alternatives or exclusion conditions are named.

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