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

Annotations only say it is a non-idempotent, open-world, non-destructive write; the description adds what actually happens: no publish occurs, a panel opens, the user submits, the app delivers to the creator's TikTok inbox with status awaiting_user_action, the prepared post expires after an hour, and the call is free but gated on an admin setting. It also warns against a specific failure mode ('must not ask the user for those settings in chat').

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 purpose is front-loaded and nearly every clause carries load-bearing information — permissions, fallback path, expiry, caption limit. It is a dense single block of long compound sentences, so it reads as a wall of text, but there is little outright waste to cut.

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 five-parameter, non-idempotent, open-world write with a human-in-the-loop handoff, the description covers the full lifecycle: prerequisite permissions, what the agent must not do, what happens after submission, how to check status, and what to do when the panel never appears. An output schema exists, yet the description still names publicationId, which is a bonus rather than a gap.

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 100%, so the baseline is 3, but the description adds real semantics beyond the schema: creativeId must be a video and never an image, omitting connectionId is only valid for single-account brands, scheduledAt must carry an offset and be in the future, and omitting it means immediate posting on submit. Only brandId goes unmentioned, though the schema covers it.

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 opening names a specific verb and resource ('Post one of the brand's finished videos to TikTok') and the body clarifies the real action: it opens Rawa's TikTok panel where the user submits. It differentiates from submit_publication explicitly. However, the claim 'there is no tool for it' sits awkwardly against the sibling submit_tiktok_post, which an agent will see in the tool list, creating a moment of doubt about which path publishes.

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 explicit prerequisites (admin must allow publishing over MCP, see get_workspace), a pre-call ritual ('Confirm the video, caption and time with the user before calling'), sibling routing (list_integrations, write_caption, list_publications, get_workspace), and a when-this-fails branch pointing at openInRawaUrl. Nothing about selecting or invoking this tool is left to inference.

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