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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the pre-post sequencing hint; it says nothing about what happens when no accounts are connected, or how the group filter affects results. With an output schema present, return shape need not be explained, so a 3 is appropriate.

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 and sequencing are front-loaded in the first clause and the platform list supports scannability. The Hungarian line is a verbatim restatement that doesn't add information for an English-operating agent, though it is short and clearly separated.

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-optional-param, output-schema-backed listing tool the essentials are present. The gap is orientation within a crowded sibling set: get_channel_options, get_integration_schema and list_groups all touch the same domain, and the description doesn't tell the agent how this result feeds into them.

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% and the single optional `group` parameter is documented there, including the explicit pointer to the list_groups tool. The description adds no parameter detail at all, so it earns the baseline 3 rather than more.

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 ('See which social media accounts (channels) the user has connected'), and the platform enumeration makes the scope concrete. However, it never distinguishes itself from closely related siblings like get_channel_options or get_integration_schema, which an agent could plausibly pick instead when looking for channel data.

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 frames the call as a prerequisite: 'before you write, preview or schedule a post', which gives a clear triggering context. It stops short of naming alternatives or exclusions, so the agent must infer that this is the 'which accounts exist' step versus the 'what options does a channel take' step handled elsewhere.

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