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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is fully carried by structured fields. The description adds the return payload shape (IDs, platform types, names), which is genuinely useful, but discloses nothing further about auth, ordering, or rate behavior. Credit is modest because the annotations do most of the work.

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 sentences, front-loaded with the action and scope, then the return payload, then the actionable next step. The platform enumeration is long but each token earns its place because no output schema exists to document the possible values.

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 present, the description correctly takes on the burden of describing what comes back: account IDs, platform enum values, and names. Given a zero-parameter list tool this is close to complete; only ordering or whether unconnected accounts are excluded is left unstated.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The mention of returned account IDs is return-value semantics rather than parameter semantics.

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?

A precise verb+resource ('List all connected social media accounts') plus an explicit scope ('across all workspaces') and a concrete enumeration of returned fields. It implicitly contrasts with the singular sibling get_social_account, but never names it, so sibling differentiation is left to inference.

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 final sentence gives a clear downstream use case — 'Use the returned account IDs when creating posts' — which tells the agent why and when to call this first. It stops short of an explicit when-not or a named alternative (e.g., get_social_account for a single account's detail), so it lands at 4 rather than 5.

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