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

Goes well beyond the annotations: discloses that it hits platform APIs and consumes rate limits, that Threads/LinkedIn are flag-gated and silently skipped rather than erroring, and that LinkedIn post-comment coverage is limited by org context and partner-tier access. Annotations only cover readOnly/openWorld/destructive hints, so this adds substantial operational context.

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?

The core action and return shape are front-loaded, then progressively finer caveats (rate limits, beta flags, LinkedIn coverage). No sentence is redundant and each adds a distinct operational fact.

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 still describes the DmSyncResult return (per-connection counts plus errors), and it covers ordering relative to the read tool, rate-limit impact, and silent-skip failure modes. Nothing needed to invoke it correctly is missing.

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 baseline is 3, but the description adds real meaning to the 'platforms' filter by explaining that Threads and LinkedIn are beta-gated per connection and that omitting platforms syncs every DM-enabled connection. It says nothing additional about workspace_id or idempotency_key, which the schema already documents well.

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 ('pulls ... into ShortSync's inbox cache'), names the platforms covered, and maps to a concrete UI action. It is clearly distinguishable from sibling list_inbox_conversations, which reads the resulting cache rather than filling it.

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?

Explicitly says to call this before list_inbox_conversations when the user asks for the latest activity, and states the consequence of skipping it (cached data from the last sync). The alternative and its selection condition are both named.

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