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

Annotations already declare readOnly=true, destructive=false, so the safety profile is covered; the description still adds real value by enumerating the returned states and the non-obvious LinkedIn edge cases (connectionPending, reconnectRequired, action_required messaging). It omits auth/permission requirements and whether the call is scoped to the current account only, which keeps it off 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?

Four tight sentences: purpose, return shape, edge cases, then scope exclusion. Front-loaded and free of restatement of the title.

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 no output schema, the description carries the return-value burden and does so by naming the state values and the LinkedIn-specific statuses. It doesn't clarify whether results are account-wide or filterable per platform, which is a small but real gap for calling it correctly.

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 coverage is 100% and the single optional platformName filter is fully described in the schema with examples. The description says nothing about the filter, so baseline 3 applies — the schema does all the work here.

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?

Opens with a specific verb+resource ('Read the authenticated account's ... integration status') and names the domains covered (advertising-channel, CRM, marketing-automation). The closing sentence explicitly scopes out connect/disconnect actions, distinguishing it from connect_channel and disconnect_channel among the 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?

The final sentence establishes the when-not boundary ('does not authorize a new connection or disconnect an existing one'), implicitly routing the agent to connect_channel/disconnect_channel. It also surfaces the launch-readiness context that makes this tool relevant before launch, though it never names those siblings explicitly.

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