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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the description's value is the added behavioral context: supported-platform enumeration, the provider field mapping, and the app-capable-host interactive-panel rendering instruction with an explicit "do NOT repeat" directive. Auth requirements and pagination are unstated, keeping this short of 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?

Front-loaded with purpose, then platform coverage, then return-field detail, and finally the output-presentation instruction. The platform enumeration is lengthy but informational rather than redundant, so each sentence largely earns its place.

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?

No output schema exists, so the description must carry the return-value burden, and it does: it names the platforms, the provider field, and the panel rendering behavior. Minor gaps remain (auth/permission prerequisites, ordering), but for a parameterless list tool this is nearly complete.

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 zero input parameters, the baseline is 4. The description adds useful semantic detail about the returned data shape (provider field, e.g. YouTube accounts use provider "google"), though this concerns outputs rather than inputs.

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 ("List connected social accounts") plus the scope/purpose ("for scheduling"). This is clearly distinguishable from sibling list tools (list_posts, list_generations, list_voices), which concern posts or media rather than connected accounts.

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?

Usage is only implied by "for scheduling" — the agent can infer it enumerates the accounts available before composing/publishing. There is no explicit when-to-use/when-not statement and no named alternative among the many sibling tools, so it meets only the minimum viable bar.

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