youtube_get_channel

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

No annotations are provided, so the description carries the full burden. It fails to disclose auth requirements (especially for 'mine'), parameter precedence when multiple are provided, or the return structure. The description only restates the basic function without deeper behavioral context.

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 concise and front-loaded with the main purpose. The args section is cleanly formatted and each line adds value, with no redundant or filler 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?

For a simple getter tool, the description covers the basic purpose and parameters. However, given no output schema and no annotations, it would benefit from mentioning auth requirements for 'mine', parameter precedence, and what the returned channel details include. The current description is minimally adequate but has clear gaps.

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%, so the description must explain each parameter. It does this well by providing examples for channel_id ('UCxxxxxxx') and handle ('@mkbhd'), and explaining the 'mine' flag. However, it doesn't clarify whether parameters are mutually exclusive or their precedence if multiple are set.

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 starts with 'Get channel details', which is a specific verb+resource combination. It clearly distinguishes itself from siblings like youtube_get_video by focusing on channels and explicitly listing three ways to identify the channel (ID, handle, or authenticated user).

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?

The usage context is clear: use this tool when you need channel details and have a channel ID, handle, or want the authenticated user's channel. However, it doesn't explicitly discuss alternatives or when not to use this tool, so it falls short of a 5.

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