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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds cost behavior beyond annotations, noting that completed lookups consume credits and repeated requests may purchase data again, but the pricing statements are internally inconsistent ('at least 10 Nexscope credits' versus '1 credit per request').

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 core purpose and return fields are front-loaded in the first sentence, which is good. The pricing boilerplate that follows is repetitive and confusing, including fragments like 'View Pricing Get Twitch user schedule 1 credit per request' that dilute the useful content.

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?

The description compensates for the absence of an output schema by listing returned event fields. However, it references cursor and trim options not present in the schema and provides contradictory pricing information, leaving the agent with an incomplete and partly unreliable picture of how to invoke the tool.

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 schema has 100% coverage for the single 'handle' parameter, so baseline is 3. However, the description claims 'pagination via cursor and a trim option for lighter responses' while the schema defines only 'handle' with additionalProperties=false; this misleads an agent into trying parameters that do not exist.

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: fetching a user's Twitch schedule by handle. It also enumerates the returned fields (start time, end time, title, description, thumbnail URL), which lets an agent distinguish this from siblings like social_twitch_profile or social_twitch_user_videos.

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 explicit guidance on when to use this tool versus alternatives such as social_twitch_profile or social_twitch_user_videos. The only implied usage is looking up a schedule by handle, with no exclusions, prerequisites, or routing conditions.

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