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

Annotations declare readOnlyHint=true, and the description adds substantial non-obvious behavior: per-account values that change when settings change, the not_supported return for non-TikTok channels, and the specific fields returned. It also warns that options.tiktok.privacyLevel has no default, which is exactly the operational detail an agent needs.

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?

Purpose is front-loaded in the first clause and the guidance is sequenced sensibly (scope, then return values, then the call-before-publish rule). The final sentence about privacyLevel is slightly long but carries required-value information that earns its place.

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 compensates by enumerating the returned fields (nickname, privacy levels, posting ability, video length limit) and the not_supported fallback. An agent has everything needed to call and interpret the response.

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 both parameters are already documented, and the description only echoes the per-account rationale for accountId and the optional nature of workspaceId. It adds no format or syntax detail beyond the schema, so the baseline 3 applies.

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 (check) and resource (channel publish requirements) and immediately distinguishes itself from the sibling 'publish' by framing it as a pre-flight check. The TikTok-specific scope is spelled out, so an agent knows exactly what it is asking for.

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?

Explicitly says 'Call it before every TikTok publish' and pre-empts the main misuse by noting that other channels return not_supported 'which is not an error to work around'. Both the when and the when-not are given.

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