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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-reach behavior are covered structurally. The description adds a useful response-size hint about filtering, but says nothing about pagination, ordering, limits, or how much history is returned.

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 tight sentences with the core capability front-loaded and the filtering tip second. No filler, though the platform-scope sentence is misleading rather than wasteful.

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 and three parameters at 0% schema coverage, the description leaves key gaps: no return-shape or pagination context, no profileId meaning, and no reconciliation of the six-platform enum against the two-platform description.

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 0%, so the description must carry the load, yet it only explains two of the three parameters ('platform', 'accountId') and never mentions profileId or clarifies what an accountId/profileId actually scopes (account vs end-user profile).

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 clear verb+resource ('Read ... direct message history') and the agent can distinguish it from the write-side sibling send_message. However, it scopes the tool to Instagram and Facebook while the platform enum also allows tiktok, whatsapp, youtube and x, so the stated purpose is narrower than what the tool actually accepts.

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 offers one concrete usage tip ('Filter by platform or accountId to keep the response small'), which is implied guidance rather than an explicit when-to-use rule. It names no alternative tool and gives no exclusion criteria for when not to call it.

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