KBK Schedule (On The Decks Next)

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

With no annotations, the description must carry the burden. It adds that the schedule 'mirrors the KBK timetable', indicating it's an exact representation, and notes it covers slots/shows/drops with times. However, it doesn't disclose potential timezone handling, caching, or data freshness issues.

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 two short sentences, front-loaded with the core purpose and a brief supporting note. No unnecessary words or repetition.

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 one-parameter tool without output schema or annotations, the description provides the essential information about what is returned (upcoming slots with times) and the timeframe implied. It could mention how 'hours' affects results, but the schema covers that. The lack of timezone/alternative guidance is a minor gap but acceptable given the tool's simplicity.

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 fully documents the 'hours' parameter with description, default, and max values. The main description adds nothing beyond the schema, so it meets the baseline for 100% coverage.

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 that the tool returns upcoming radio slots/shows/drops with start and end times, which matches the tool name 'get_schedule'. It distinguishes from siblings like get_next_drop by covering the full upcoming schedule rather than just the next item, though it doesn't explicitly name the alternative.

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 mention of when to use this tool versus alternatives like get_next_drop or list_channels. The only hint is 'Mirrors the KBK timetable' implying it's the full schedule, but there is no explicit guidance or condition for selection.

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