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

The annotations already declare non-read-only, idempotent, non-destructive behavior. The description adds valuable context beyond them: it is a full-set replacement operation, an empty list removes the limit, defaults are capped per platform, and account IDs are validated against the organization before the transactional update. This is strong transparency without contradiction.

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?

The description is compact and front-loaded: purpose first, then replacement semantics and default-selection rules, then validation. Every sentence carries operational information and none merely restates the schema or annotations.

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 five parameters, 60% schema description coverage, and no output schema, the description covers the critical behavioral points: scope, replacement semantics, empty-list behavior, defaults, and validation. It could be more complete by pointing agents to list_social_accounts for account IDs or by stating expected return/error behavior.

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 schema documents brand_id, site_id, and user_goal, while the description compensates for the undocumented connection_ids/default_connection_ids by explaining complete-list replacement, empty-list clearing, and the per-platform default cap. It does not explain the maxItems limit or where account IDs should come from, but it adds meaningful semantics beyond the schema.

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 uses a specific verb ('Choose the full set') and names the resource and scope ('connected accounts this brand (or the supplied site) may publish to'). It is clear, but it does not explicitly contrast the tool with relevant siblings such as list_social_accounts or set_profile_accounts, so it falls short of a 5.

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?

It gives invocation guidance: pass the complete list each time, an empty list removes the limit, and default_connection_ids marks a pre-selected account. However, it does not explicitly say when to use this tool versus alternatives or name any exclusions, so usage is implied rather than fully specified.

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