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

No annotations are provided, so the description carries the full behavioral burden; it does disclose the read-only nature and that each account comes with status, which is genuinely useful. It says nothing about what statuses exist, whether disconnected accounts appear, empty-state behavior, or auth/permission requirements for reading publishing accounts.

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 compact sentence that front-loads what is returned (LinkedIn/Instagram accounts) and closes with the safety trait. Nothing is wasted and nothing needs reordering.

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 no-parameter, read-only list tool with no output schema, the description covers the essentials: what the collection is, which platforms, that status is included, and that it is safe. The remaining gap is enumerating what the status values mean and whether unconnected accounts are included.

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 of 4 applies; there is no argument semantics that need explaining. The description correctly implies an unfiltered list of all connected publishing accounts.

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?

Names a specific verb (list) plus resource and disambiguates the otherwise opaque term 'content accounts' as LinkedIn/Instagram accounts connected for publishing, with the Settings → Social location. It does not, however, explicitly differentiate itself from nearby siblings like list_linkedin_accounts or list_whatsapp_accounts, leaving the agent to infer the boundary.

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 read-only tag implies this is the safe inspection call before connect_content_account/disconnect_content_account, but that is left implicit. There is no statement about when to prefer this over list_linkedin_accounts, crm_list_linkedin_accounts, or list_whatsapp_accounts.

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