Connect Twitch EventSub bus

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

Annotations already establish readOnlyHint=false, openWorldHint=true, destructiveHint=false, so the safety profile is known. The description adds a list of scaffold contents but does not disclose side effects, permission requirements, or what happens to existing components. This adds moderate context without contradiction.

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 a single, front-loaded sentence that efficiently lists the scaffold's major components without wasted words. It is appropriately sized and clear.

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 11 parameters, no output schema, and only 18% schema description coverage, the description leaves significant ambiguity. It does not explain parameters, return values, or operational context, making it incomplete for an AI agent to invoke the tool 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?

Schema description coverage is only 18% (just name and parent_path). The description does not explain any of the 11 parameters, though it vaguely references 'reward maps' and 'moderation policy' that could map to reward_count and moderation_level. It fails to compensate for the low schema coverage.

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 uses the specific verb 'Create' and identifies the resource as a 'Twitch EventSub/chat scaffold' with enumerated components (sanitized event rows, reward maps, moderation policy, adapter source, OAuth/webhook safety notes). This clearly distinguishes it from the many sibling connect_* bus tools and makes the tool's function unambiguous.

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?

No guidance is provided about when to use this tool versus siblings like connect_youtube_live_chat_bus or connect_tiktok_live_events_bus. The description only states what it does, not when to choose it, and no alternatives or exclusions are mentioned.

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