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

Annotations only declare readOnly/non-destructive/openWorld=false; the description adds the substantive behavior an agent actually needs: per-platform capability matrix (Threads/LinkedIn comment scopes, IG/FB-only DMs, like-scope always false for three platforms) and the meaning of needs_reconnect (missing scopes or token flagged). This is exactly the context the annotations cannot carry.

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?

Purpose and usage are front-loaded in the first two sentences, then the row fields. The second sentence is a dense chain of nested parentheses that would scan better as a short list, but every clause carries platform-specific information an agent would otherwise have to guess.

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?

There is no output schema, so the description does the work of documenting the returned row shape (has_comment_scope, has_messaging_scope, has_like_scope, needs_reconnect) in detail. Combined with the explicit downstream-tool gating, an agent has everything needed to call it and interpret results.

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?

Single parameter with 100% schema description coverage, including the 'get one from list_workspaces' hint already in the schema. The description adds no further meaning about workspace_id, so 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?

States a specific verb and resource ('Lists the workspace's platform connections') and narrows scope to those 'wired into the DM inbox', listing the platforms covered. This scope language distinguishes it in substance from the sibling list_platform_connections, but that sibling is never named, so the differentiation is implicit rather than explicit.

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 two concrete use cases ('which accounts can I reply to?' and pre-flight check before sync_inbox or reply_to_comment), naming the downstream tools it gates. It lacks an explicit 'do not use this for X, use list_platform_connections instead' exclusion, which is the one gap for this tool family.

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