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

Annotations already declare openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is largely covered. The description adds genuinely non-redundant context: this route is panel-internal and its payload is the user's own panel settings and declarations, so the agent must not synthesize them. It does not say what actually happens on publish (visibility, failure modes).

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 short sentences with the scope stated first and the hard prohibition second; nothing is wasted and the most actionable constraint is front-loaded.

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 tool the agent is explicitly told never to invoke, the essential information is the prohibition and the panel origin, both present, and an output schema exists so return values need no explanation. The missing piece is the routing target when the agent does need to publish.

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?

Nine required parameters with 0% schema description coverage, and the description supplies no per-parameter meaning, allowed values, or the semantics of token/consent/brand toggles. 'The settings and declarations the user made there' gestures at the origin of the values but does not compensate for the coverage gap.

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 and resource ('posts' a TikTok post) plus a scope qualifier ('Internal to the Rawa TikTok panel'), which implicitly separates it from the public prepare_tiktok_post/submit_publication route. It doesn't explicitly name those siblings, so an agent must infer the distinction rather than read it.

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 prohibition and the strongest possible when-not guidance. It stops short of a 5 because it never names the alternative the agent should use instead (presumably prepare_tiktok_post), leaving the redirect to inference.

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