Get TikTok publishing settings

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

Beyond the readOnlyHint annotation, the description adds valuable behavioral context: TikTok narrows privacy values per account, invalid values are not merely rejected but fail with a specific error_code, and the tool returns account-specific fields. This gives the agent a clear model of what to expect and why the call matters.

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 description is two sentences with no filler. It front-loads the core meaning, then packs the prerequisite, failure mode, and returned content into a compact, information-dense structure.

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 single-parameter read-only tool with a full input schema and an output schema, the description is complete. It covers when to call it, why it matters, what it returns, and how it behaves under invalid input. 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 description coverage is 100%: the single `profile` parameter is already documented as an Upload-Post profile name with a TikTok account connected. The description adds no additional parameter-level semantics, so the baseline of 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?

The description clearly identifies the resource (the connected TikTok account's publishing settings) and the tool's function: returning what the account is allowed to publish, including privacy_level_options and other settings. It is specific and easily distinguishable from sibling tools like upload_video or tiktok_music_search.

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?

The description explicitly instructs calling this tool before setting `tiktokPrivacyLevel`, and explains the failure mode if an unsupported privacy value is used. This is a strong, actionable usage prerequisite with the rationale attached, leaving no ambiguity about when it should be invoked.

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