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

Annotations only supply readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds real context beyond that: it needs only read:accounts, is free, and involves a human-in-the-loop browser sign-in rather than an API-side action. It also documents the Snapchat flow semantics (no silent API post, no Snapchat ads product in Soclo) and a specific error code. It does not address link lifecycle (expiry/single-use), which matters given idempotentHint=false.

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, permissions and the X Ads note are front-loaded, which is good, but the Snapchat paragraph is bloated and partly tangential — it explains how personal Snap sharing works through the app editor and repeats the 'never a silent API post' point twice. Several sentences could be cut without losing invocation-relevant 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?

An output schema exists, so return-value explanation is rightly omitted, and the description covers the platform-specific edge cases that would otherwise trip an agent (X Ads accountId, Snapchat profile selection, no_aggregator_profile recovery). Coverage of the other listed platforms (instagram, facebook, tiktok, etc.) is left to the implicit default flow, which is a minor gap.

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%, so both platform and accountId are already documented in the schema. The description adds the X Ads-specific meaning of accountId (owned X posting account), which mirrors the schema text, but supplies no extra syntax or format detail. Baseline 3 is appropriate when the schema carries the parameter burden.

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?

The first sentence states a specific verb+resource+outcome: it returns the real Soclo connect link for a named platform, which the owner opens in a browser to sign in. It is clearly distinguishable from soclo_accounts_list (enumerate existing accounts), soclo_accounts_disconnect (remove one), and soclo_accounts_bootstrap (referenced only as an error-recovery step).

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?

It gives real routing guidance: pass accountId for X Ads, use the owned X posting account from soclo_accounts_list, and run soclo_accounts_bootstrap first if the call returns no_aggregator_profile. It stops short of an explicit 'use this when you want to add a new account, not to inspect or refresh existing ones' statement, so the when-not condition is only implied.

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