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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered; the description adds real behavioral context on ordering ('newest activity first') and pagination mechanics ('pass the returned cursor to get the next page'). It does not describe the shape or size of an individual conversation record, but the added pagination/ordering detail goes beyond the annotations.

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?

The core operation and ordering are front-loaded, followed by pagination mechanics and the sibling routing. The long parenthetical platform inventory is dense but each item is load-bearing for scope. Slightly heavy in one sentence, but 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 still tells the agent the ordering and the cursor-pagination contract, and the six optional filters are fully documented in the schema. Combined with annotations covering the read-only profile, nothing essential for correct invocation 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?

Schema description coverage is 100%, with the 'unanswered' filter even spelled out in detail at the schema level, so the description does not need to re-explain parameters. It adds no syntax or format nuance beyond what the schema already provides, making the baseline 3 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+resource ('List social inbox conversations') and enumerates exactly which sources are covered (IG/FB DMs, comments, mentions, LinkedIn, TikTok, YouTube, X, Threads). It also draws the boundary against the nearest sibling by contrasting bulk listing with one-at-a-time triage. An agent can identify the tool without opening the 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?

It explicitly routes the agent to get_next_unanswered when the goal is working through items one at a time, which is a clear when-to-use-alternative statement. It stops short of covering other adjacent siblings (get_inbox_conversation, mark_inbox_read) or when to prefer the 'unanswered' filter over the sibling triage tool, so it is clear but not exhaustive.

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