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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond that: the Social publishing aggregation caveat and the fact that 'connectionId' is the provider name consumed by sync_connections, update_connection_settings, disconnect_connection and get_connect_link.

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?

Content is front-loaded with what is listed, then the scoping caveat, then the clarifications. It is fairly dense and the trailing 'Related:' list is a bit listy, but every sentence carries signal.

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?

An output schema exists, so return values need not be described, and the description covers the aggregation subtlety and the cross-tool identifier semantics. The only minor gap is pagination or result ordering, which is not addressed.

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. The description still explains the semantics of the connectionId identifier that this listing surfaces and how downstream tools consume it, adding meaning beyond the empty 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?

States a specific verb and resource ('Lists integrations') plus the exact payload fields returned (health, last sync, failed jobs). It explicitly frames itself against the sibling 'list_channels', so an agent can distinguish the two without opening either schema.

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 states what it does NOT show (individual LinkedIn/Instagram accounts) and names the alternative to use instead ('call list_channels for that'). It also clarifies that connecting happens out-of-band via get_connect_link and sync_connections, covering when-not and alternatives.

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