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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so 'Free; changes nothing' is partly redundant. The description nonetheless adds the auth scope requirement ('Needs read:inbox') and discloses what the listing contains, which the annotations do not cover.

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 compact sentences that front-load the resource and payload, then the auth requirement and filters. Every clause carries information and there is no filler.

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 compensates by naming the returned fields, and it covers the auth scope and filterable dimensions. Pagination (limit/cursor) behaviors exist in the schema but are undocumented; status is hedged as 'if the app supports it' in the schema, which the description does not acknowledge.

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 description coverage is 100%, so all five parameters are already documented, including the accountId cross-reference to soclo_accounts_list. The description adds only a bare restatement of the three filter params and omits limit/cursor entirely, so the baseline 3 is appropriate.

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 ('List conversations from the Soclo app's Inbox') and enumerates the key payload fields (platform, contact, last message preview, unread count). It is distinguishable from the inbox comment/mention/review siblings by the 'conversations' framing, but it never names those siblings explicitly.

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?

Gives the optional filter dimensions (accountId, platform, status) and a prerequisite ('Needs read:inbox'), which implies when the tool is applicable. However, it gives no explicit routing guidance against the many sibling inbox tools (soclo_inbox_messages, soclo_inbox_comments, soclo_inbox_mentions).

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