List KBK Channels & Genres

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

No annotations are provided, but the description carries the burden by emphasizing this is the 'real' structure and providing a caution against inventing data. It implies a read-only, authoritative enumeration, which is sufficient for a zero-parameter static list tool.

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?

Two terse sentences: the first declares the content, the second the usage context. No wasted words, easy to parse quickly.

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, parameterless list tool with no output schema, the description fully covers its purpose and usage context. The sibling tools show this is a reference among dynamic APIs, and this description positions it appropriately.

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 tool has zero parameters, so a baseline of 4 is applied. The description adds no parameter-specific detail because none exist; the schema is empty and fully covered.

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 lists the KBK channel structure, genres, mapping, and colors. The verb 'list' and specific resource ('KBK Channels & Genres') make the purpose unambiguous, and it distinguishes itself from siblings like get_now_playing or play_channel.

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?

Explicit guidance is given: 'Use this to avoid inventing channels/genres that do not exist.' This tells the agent when to consult this tool. It doesn't state alternatives, but the instruction is clear enough for a reference tool.

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