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

Annotations already declare the safe-read profile (readOnlyHint, destructiveHint false, openWorldHint false), so the description only needs to add scope context — and it does, disclosing the fixed 7-day window, the set of connected accounts included, top 10 posts, and daily trend series. It stops short of noting freshness/latency or whether the window is configurable.

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 sentences, zero filler, with the purpose front-loaded and the content enumeration immediately after. Every clause earns its place by telling the agent what the aggregate contains.

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, the description does the work of explaining the return shape (accounts, 7-day metrics, top 10 posts, daily trends), which is exactly what an agent needs to judge applicability. Minor gaps remain around data freshness and whether the 7-day window can be adjusted.

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 100% for the single workspaceId parameter, so the schema already carries parameter meaning and the baseline of 3 applies. The description says 'for a workspace' but adds no format, source, or validity constraints beyond the 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?

States a specific verb and resource (aggregated analytics overview for a workspace) and enumerates the payload contents, which separates it conceptually from account-level siblings like get_account_analytics. It does not, however, explicitly name those siblings or state the workspace-vs-account distinction as a routing rule.

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?

Usage is implied: reach for this when you need a broad workspace-level snapshot rather than per-account or per-post detail. There is no explicit when-to-use, when-not-to-use, or named alternative among the many analytics/list siblings, so the agent must infer the selection rule.

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