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

Annotations only declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true; the description goes well beyond that by disclosing the 24-hour messaging window, that Threads has no DMs, the two-step preview/confirm safety flow with preview_id, and the 30s/60s sync cooldown. These are material behavioral traits an agent needs before calling, and none of them contradict 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?

Dense but well-organized: it front-loads the tool's purpose and access requirement, then groups details by action. Every clause carries information, though the single long block sentence is slightly harder to scan than a broken-out structure would be.

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 multi-action mutation tool with no output schema, the description covers everything needed: which actions exist, their required inputs, the preview/confirm return-handshake (preview_id), platform constraints, rate limits, and account prerequisites. Nothing essential 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 coverage is already 100%, so the baseline is 3, but the description layers on meaning the schema does not: it ties confirm to the preview_id flow, explains the cooldown semantics of sync, notes sync_type defaults and the comments-only limitation of Threads/LinkedIn, and points to provenance tools for account_id and conversation_id. This meaningfully exceeds the schema's terse field hints.

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?

The description opens with a specific verb+resource ("Act on the social inbox") and enumerates the two concrete actions with their targets (Instagram/Facebook Page DM replies, pull inbox data for four platforms). It distinguishes itself from siblings by naming the related tools (list_conversations, list_accounts) that supply its inputs, so an agent can place it correctly in the toolset.

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 gives strong conditional guidance: plan requirement (Pro or higher plus posts:write), the preview-then-confirm protocol for send, the 24-hour window, and per-platform cooldowns. It stops short of explicitly stating when NOT to use it versus alternatives such as list_conversations or manage_comment, so it is clear context without full exclusion guidance.

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