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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that by disclosing the shape of the payload — accounts, groups, and per-network publishing constraints — which is the real reason to call it. It does not mention auth requirements or result size, keeping it 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?

A single dense sentence that front-loads the returned data, followed by the sequencing instruction. The parenthetical examples ('one business's Instagram + YouTube') resolve ambiguity about what a group is without padding.

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?

There is no output schema, so the description must carry the return-value burden — and it does, naming the three data categories and the per-network constraint fields. Combined with annotations covering the read-only profile, an agent has everything needed to call this correctly as a first step.

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 the baseline is 4; there are no argument semantics to explain. The description correctly implies a no-argument, whole-account-listing call and instead spends its words on output shape.

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?

The description concretely enumerates what is returned: connected accounts (id, network, handle), account groups, and per-network requirements (caption limit, media type, settings). That is far more specific than a generic 'list' restatement and clearly separates it from create_draft/list_posts. It loses a point because the verb is only implicit in the name and it references 'publish_post', which is not among the listed siblings.

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?

Explicit sequencing is given: 'Call this first, then pass a group name or account handles to create_draft or publish_post.' That tells the agent both ordering and the downstream consumer of the returned handles/groups. No exclusion conditions are stated, and the reference to publish_post (not in the sibling set) could send an agent toward a tool that may not exist.

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