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

Annotations already establish readOnly/non-destructive, and the description adds real behavioral context beyond them: the not_supported behavior for other channels, that values are per-account and drift when the person edits TikTok settings, and that privacyLevel has no default so this call is the source of that value.

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?

Three dense sentences that are front-loaded with the scope restriction, then the return contents, then the pre-publish requirement and the privacyLevel dependency. No filler.

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, the description carries the burden of describing return fields (nickname, privacy levels, postability, video length limit) and does so, plus it explains the one cross-field dependency (privacyLevel required, no default). Nothing needed for correct invocation 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 100%, so the baseline is 3, but the description adds rationale the schema only implies – that these values are per-account (justifying required accountId) and that workspaceId should be omitted rather than re-asked when already decided. It stops short of adding format/syntax detail beyond the schema.

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 resource (TikTok creator publish settings) and a clear verb (get), and explicitly scopes itself as TikTok-only, which distinguishes it from the broad publish/publish_now siblings. An agent can tell what it returns without opening the schema.

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?

Gives explicit when-to-use ('call it before every TikTok publish'), explicit when-not ('do not call it for any other channel'), and even pre-empts a wrong reaction to the not_supported response ('which is not an error to work around'). This is exactly the routing guidance an agent needs.

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