Connected social accounts

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond them: connections are scoped per workspace, and this call cannot initiate OAuth. It does not describe return shape or pagination, but for a simple read that gap is minor.

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?

Three short sentences, front-loaded with what is returned, then scope, then the OAuth constraint. No sentence is redundant and nothing is buried.

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?

For a read-only, single-parameter list tool with no output schema and full annotation coverage, the description supplies what an agent needs: the platforms, the per-workspace scoping, and the inability to connect accounts. Only the return format is left unspecified, which is acceptable here.

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?

With 100% schema description coverage on the single workspaceId parameter, the schema already documents defaulting and per-call override behavior. The description's 'Connections are per workspace' reinforces the parameter's meaning but adds no syntax or format detail, so the baseline of 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 resource (TikTok, Instagram and YouTube accounts connected to this workspace) and its scope, so an agent immediately knows what it returns. Enumerating the platforms and 'per workspace' scope distinguishes it from siblings like disconnect_account and from generic workspace tools.

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?

The description provides an explicit when-not: connecting new accounts can only happen in the browser and this tool cannot start an OAuth flow, which prevents a likely mis-invocation. It implies usage through 'the ids that scheduling tools need' but never names the sibling that would help route the agent further.

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