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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new context by disclosing the returned metric categories and the notable behavior that output is 'platform-specific data format', but it says nothing about permissions, rate limits, or whether a date range is implied or defaulted.

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?

Three short sentences that are front-loaded with the core purpose and then the payload contents; no filler or repetition of the title. It could be tighter, but every sentence carries information.

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 correctly takes on the burden of describing return values, naming both account-level and post-level metrics plus the platform-specific format caveat. The remaining gap is routing context (time range or when to prefer get_analytics_trends), which is a modest omission for a two-parameter read tool.

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 both parameters, so the schema already explains workspaceId and socialAccountId. The description adds no parameter-level meaning (no ID format, no note that both are required, no scope caveats), which is the expected baseline when the schema does the work.

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 data for a specific social account') and enumerates the metric families returned (followers/following, views/likes/comments/engagement rate). It is clear on its own, but it never distinguishes itself from siblings like get_analytics_trends or get_brand_overview, leaving the agent to infer which analytics tool to pick.

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?

There is no when-to-use or when-not-to-use guidance, and no mention of the two obvious alternatives in the sibling set (get_analytics_trends, get_brand_overview). The agent gets no signal about whether this is the per-account snapshot versus the trend or brand-level view.

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