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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety behavior is covered. The description adds no behavioral context beyond those annotations—no mention of data freshness, window behavior, rate limits, or what a snapshot contains—so it does little work here.

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?

Two short sentences, front-loaded with the action and then the parameter constraint. Efficient and free of filler, though the second sentence is largely a restatement of the schema's required/enum constraints.

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 3-parameter read-only tool with no output schema, the description need not explain return values, but it leaves gaps: it never mentions the 'window' parameter, gives no sense of what snapshots include, and does not route the agent away from refresh_analytics.

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 only 33%, so the description must compensate, and it partially does by explaining that 'scope' must be post/account/run and that 'id' is the matching identifier. However, the optional 'window' parameter is never mentioned, leaving a real coverage 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?

States a specific verb and resource ('Get analytics snapshots') and enumerates the three possible scopes, so the agent understands it is a targeted analytics fetch. It does not, however, distinguish itself from the sibling refresh_analytics, which is the most likely confusing alternative.

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 you call it to fetch analytics for a post/account/run and restates that scope and id are required, which is implied usage. It gives no explicit when-to-use, when-not-to-use, or alternative selection guidance (e.g., versus refresh_analytics).

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