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

Annotations only cover the safety profile (readOnly/openWorld/non-destructive), and the description adds substantial behavioral context: live-fetch latency, a possible 24h snapshot staleness for X with the billing rationale, the LinkedIn personal-profile permission limitation, which platforms actually expose metrics, and the required analytics:read scope.

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?

Well front-loaded — the core purpose and the list_posts routing come first, caveats after. It is dense and long, but nearly every clause (snapshot staleness, metric availability, duration_seconds, output block) carries actionable information, so little is wasted.

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 carries the return-value burden and does so thoroughly: a summary table plus a 'Structured data' JSON block with stable post id, permalink, untruncated caption, and exact-integer metrics. Combined with the per-platform metric caveats, an agent has everything needed to call and consume it.

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 100%, so the schema already documents both params, giving a baseline of 3. The description reinforces why limit defaults differ for X (billing) and clarifies platform-filtering intent, adding marginal value over the schema rather than restating it.

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+resource ('Fetch the user's most recent posts') with precise scope ('straight from their connected platform APIs... INCLUDING content published outside OmniSocials'). It explicitly distinguishes itself from the sibling list_posts, so an agent can separate the two without opening either schema.

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?

Gives an explicit trigger condition: 'Use this when list_posts is empty — e.g. a brand-new workspace that has not published through OmniSocials yet.' The alternative (list_posts) is named and the selecting condition is spelled out, leaving nothing to inference.

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