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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so 'Read-only; no side effects' adds nothing. However, the description does disclose substantive behavior beyond annotations: entries carry a connected flag, company pages are keyed by company_page_id while connected X/Threads accounts each appear as separate entries keyed by connector_account_id, and is_default marks the default — exactly what an agent needs to choose a valid target.

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?

Two sentences, front-loaded with the core purpose and then the entry structure. The closing 'Read-only; no side effects' is redundant with the annotations and is the one clause that does not earn its place.

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 zero-parameter list tool with full annotation coverage and an output schema, this description covers what is not inferable from structured data: which account types appear, the connected/default flags, and the two different id fields. Nothing needed to call it correctly or interpret the identifiers is missing.

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 is no parameter semantics to add, and the description correctly spends its space on output-shape guidance instead.

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 the posting accounts the user can publish to') and then enumerates the exact contents: personal LinkedIn/X/Threads accounts plus administered LinkedIn company pages. This scope is precise enough to separate it from neighbouring tools like connect_platform (which adds accounts) without needing to name them.

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 phrase 'accounts the user can publish to' implies this is the discovery step before create_post/publish_post, but no explicit when-to-use statement or alternative is given. Usage is inferable rather than stated.

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