Connect TikTok Live events bus

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

The description enumerates the scaffold's contents (gift tiers, moderation policy, adapter source) but does not disclose behavioral aspects like whether it creates new nodes, modifies existing components, or requires external credentials. Annotations indicate it's a non-read-only, non-destructive, open-world operation, but the description adds minimal behavioral context beyond that.

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 single sentence is densely packed with relevant terms and front-loaded with the core action. It avoids filler words, though jargon like 'sanitized event rows' may be unclear to agents unfamiliar with the domain.

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 with 9 parameters and no output schema, the one-sentence description is insufficient. It doesn't explain what 'scaffold' means in this context, how the result integrates with the project, or what 'sanitized event rows' and 'auth/client safety notes' entail, making it hard for an agent to use correctly.

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?

With only 22% schema description coverage, the description compensates by referencing concepts like 'gift tiers' (gift_tier_count), 'moderation policy' (moderation_level), and 'adapter source' (adapter_url/adapter_mode). However, it omits several parameters such as name, active, parent_path, and creator_label, leaving them unexplained.

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 states the action ('Create') and resource ('TikTok Live-style event scaffold'), and lists specific components such as 'sanitized event rows, gift tiers, moderation policy' that differentiate it from generic bus tools. However, it does not explicitly distinguish it from sibling event bus tools like connect_twitch_eventsub_bus.

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?

There is no guidance on when to use this tool versus alternatives. The description only explains what it builds, leaving the agent to infer usage from the tool name and context. No exclusions or alternative recommendations are provided.

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