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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds the non-obvious context that this is bound to an in-progress panel session rather than a general resource, but says nothing about what the token represents or what the returned draft contains.

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?

Very short and front-loaded, which is right for a tool agents should not call. But the sentence fragments awkwardly ('Internal to the Rawa TikTok panel: the post it is finishing'), spending words on identity rather than on what the tool returns.

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?

An output schema exists so return values need not be explained, but the core gap is the undocumented token and the ambiguous object being fetched. For a tool that agents are told to never call, the description still needs to be complete enough for a panel-integrated caller to know what token to pass.

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?

The single required 'token' parameter has 0% schema description coverage, and the description never mentions it. An agent has no idea whether the token is a session id, an upload id, or a publication id.

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 phrase 'the post it is finishing' gestures at returning a TikTok draft but never states a verb or resource plainly. It does differentiate itself from siblings like prepare_tiktok_post by declaring itself panel-internal, but an agent cannot tell what it actually returns.

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?

'Never call this yourself' is an unambiguous exclusion that no sibling offers, which is exactly the routing signal an agent needs. It stops short of naming what to call instead (submit_tiktok_post or prepare_tiktok_post would be the natural alternatives), so it is not a 5.

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