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

Annotations already declare readOnlyHint=true and destructiveHint=false, yet the description adds substantial non-obvious behavior: never assume PUBLIC_TO_EVERYONE is available, outputs are the same shape for Business connections, a VIDEO on a business connection can only publish public, and tiktokOptions.uploadAsDraft is the sole exception. Those are exactly the caveats an agent would otherwise get wrong.

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?

It is front-loaded with the three key returned capabilities before the usage rule and the business-connection caveat, so the most important content comes first. The final sentence is a dense run-on with three nested parentheticals, which costs some readability but each clause still carries information.

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 an output schema present, the description need not enumerate return fields, and it correctly spends its words on the semantic traps instead. Coverage is strong for a read-only tool; the main omission is failure modes (expired connection, missing TikTok scope, error behavior), which would help an agent recover rather than just interpret success.

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%, so both parameters (organizationId and platformConnectionId) are already documented in the schema, including the multi-org requirement. The description only echoes the list_platform_connections provenance and adds no format, format-of-id, or selection nuance beyond the schema; baseline 3 is appropriate.

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 first sentence names a specific verb and resource ('Read what a connected TikTok account allows right now') and enumerates exactly what is returned: privacy_level_options, comment/duet/stitch availability, and max video length. It is clearly distinguishable from siblings like get_platform_availability or list_platform_connections, which deal with connection lists or platform-level capability rather than per-account TikTok posting options.

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?

It gives an explicit usage rule ('Ask the user which privacy level to use; TikTok does not allow a default to be chosen for them') and points to list_platform_connections with the authMethod "business_api" marker as the way to determine connection type. What it lacks is an explicit statement of when to call this versus create_post/validate_post, though the posting-decision context makes that inference easy.

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