list_youtube_topics

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

The description fully discloses behavior: lists ~470+ entries, includes channelCount, takes no parameters, costs 1 credit, and is YouTube-only. No annotations exist, so the description carries the full burden and meets it.

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 informative, but could be slightly more structured. It front-loads the main action and details, with minimal waste.

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 tool has no parameters and no output schema, the description provides complete context: what it returns, its limitations, and cost. No gaps remain.

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?

No parameters exist; schema coverage is 100%. The description adds value by explicitly stating 'Takes no parameters' and explaining the output content (topics with channelCount), earning a baseline 4.

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 explicitly states it lists the full YouTube topic taxonomy with channelCount per topic, and distinguishes it from sibling tools like get_youtube_profile. It also notes that Instagram and TikTok lack a topic taxonomy, reinforcing its unique scope.

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?

It clearly states when to use (to see full taxonomy) and when not to (for a specific creator's topics, use get_youtube_profile). It also mentions cost (1 credit) and platform specificity.

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