Get link to connect social accounts

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

Goes well beyond the annotations: discloses the hidden side effect of creating a 'default' profile when none exists (consistent with readOnlyHint=false), the 48-hour link validity, and the branch where an existing profile yields the dashboard link instead. Rate limits and auth requirements are not covered, keeping it from a 5.

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?

Four sentences, each doing distinct work: purpose, trigger conditions, branching behavior, and the post-call workflow. The purpose and the user-facing action are front-loaded.

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 values need no elaboration, yet the description still names the `connect_url` field the agent must surface. For a zero-required-parameter, side-effecting tool, nothing an agent needs to call it and act on the result 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 both parameters are already documented. The description adds only indirect meaning (that 'profile' refers to an existing profile and platforms examples), so baseline 3 is appropriate.

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 ('Get the link the user opens to connect (or reconnect) social accounts') with concrete platform examples. It is clearly distinct from sibling read tools like get_account_info or get_platform_metrics.

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 names the trigger conditions ('when list_users shows no profile, or the platform is not connected or needs reconnecting') and specifies the follow-up sequence (give connect_url, wait, call list_users to confirm before publishing). Alternatives and when-not are implied by the prerequisites.

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