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

Annotations already establish readOnlyHint/destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavioral detail beyond that: which platforms return populated engagement data (Twitter, Instagram) versus publish status + URL only (LinkedIn, Threads, TikTok), preventing misread empty results.

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 waste. The core purpose is front-loaded and the platform limitation follows as a compact parenthetical caveat.

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 an output schema present, return-value documentation is not needed, and the platform-behavior note covers the main interpretive risk. The only gap is the unspecified nature/format of postId, a minor omission for an otherwise complete single-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 coverage is 0% and the single postId parameter is undocumented in both schema and description. The parameter is largely self-explanatory from its name and the 'published post' framing, but the description says nothing about id format or origin (internal id vs. platform id).

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 ('Fetch') and resource ('engagement metrics (likes, comments, shares, impressions) for a published post') with an explicit scope of 'across every platform it was sent to.' This distinguishes it in substance from channel-level analytics siblings like get_channel_analytics, though no sibling is named.

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 published-post scope implies when to reach for this tool, and the platform caveat hints at what not to expect. However, it never names an alternative (e.g., get_channel_analytics for per-channel breakdowns or get_post for content) or states exclusions, leaving routing to inference.

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