twitch_get_clips

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds nothing beyond that—notably it never mentions that client_id and client_secret parameters imply an authentication requirement, nor anything about pagination or result volume.

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 front-loaded with zero waste, so it is concise in the literal sense. That concision comes at the cost of under-specification rather than efficiency—one more clause about credentials or the game_id filter would have earned 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 five undocumented parameters, no output schema, and an authentication-sensitive surface, the description leaves too much to inference. It doesn't need to explain return values, but it should at minimum cover credential handling and what the optional filters do.

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 0% across all five parameters, so the description must carry the burden and does not. Only broadcaster_id is obliquely implied by 'for a Twitch broadcaster'; first, game_id, client_id, and client_secret are entirely unexplained (page size, filtering by game, credential handling).

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 states a specific verb and resource (get clips) scoped to a Twitch broadcaster, which is more informative than a bare name restatement. It doesn't, however, distinguish this from Twitch siblings like twitch_get_stream or twitch_channel_info, which an agent would also consider for channel-level data.

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 statement of when to use this tool versus the many related Twitch siblings, nor any prerequisite context. An agent must infer from the name alone that this retrieves clip listings rather than streams, games, or schedules.

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