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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is fully covered structurally. The description adds that results are ranked by value and which metrics are included, which is useful, but it says nothing about look-back defaults, data freshness, or whether platforms with no data appear.

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, front-loaded with the metric list and the ranking behavior, then the intended use. No filler, no restatement of the tool name or title.

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 usefully enumerates the returned metrics, which partially compensates. But it omits how the ranking is computed, what the look-back window default means for interpretation, and how it relates to get_analytics_overview — gaps that matter in a toolset with this many overlapping analytics siblings.

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% and the single `days` parameter is fully documented in the schema (range, default, meaning), so the description carries no additional burden here. It adds no format or interpretation guidance beyond the schema, so the baseline 3 applies.

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 names a specific verb+resource (per-platform breakdown of performance) and enumerates the metrics returned (views, reach, engagements, followers, engagement rate), so an agent knows exactly what this returns. However, it never distinguishes itself from close siblings like get_analytics_overview, get_follower_stats, or get_top_performing_media, leaving the agent to infer the difference from names alone.

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?

"Use it to decide where to focus" implies strategic/planning usage, which is a real signal beyond the name. But there is no explicit when-not, no named alternative, and no prerequisite (e.g., connected platforms) stated, so the agent must still guess between this and the many other analytics siblings.

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