twitch_channel_info

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

The description implies a read operation but fails to disclose authentication requirements (client_id and client_secret are optional in schema but likely needed) or what data is returned. With no annotations, this omission is significant.

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 extremely concise (6 words) but underspecified. It lacks structure and does not provide enough detail for a tool with three parameters and no annotations.

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?

Given the lack of output schema, annotations, and parameter descriptions, the description is far from complete. It omits authentication info, return value details, and any guidance on using the optional parameters.

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?

The input schema has 0% description coverage, and the description adds no meaning to the parameters. It does not explain what broadcaster_id is or how to obtain it, nor the role of client credentials.

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 tool gets information about a Twitch channel, using a specific verb and resource. However, it doesn't specify what kind of information (e.g., profile, followers) nor differentiate from other Twitch tools like twitch_get_stream.

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 on when to use this tool vs alternatives such as twitch_get_stream or twitch_get_clips. There is no mention of prerequisites or context.

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