TV On The Air

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 states 'Get TV shows currently on air', implying a read-only operation, but doesn't disclose any behavioral traits such as rate limits, authentication needs, pagination behavior, or what 'currently on air' means in terms of time window. This is a significant gap for a tool with no annotation coverage.

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 a single, efficient sentence that front-loads the core purpose without any wasted words. It's appropriately sized for a simple tool and earns its place by clearly stating what the tool does.

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 complexity of a tool that fetches real-time TV data, no annotations, and no output schema, the description is incomplete. It doesn't explain what 'currently on air' entails (e.g., live vs. scheduled), how results are formatted, or any limitations, making it inadequate for an agent to use effectively without additional context.

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 description adds no parameter semantics beyond what the input schema provides. With 100% schema description coverage, the schema already documents the 'page' parameter fully. The description doesn't explain how pagination relates to 'currently on air' shows or any other contextual details, so it meets the baseline but adds no extra value.

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 'Get TV shows currently on air' clearly states the verb ('Get') and resource ('TV shows currently on air'), making the tool's purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'tv_airing_today' or 'trending_tv_day', which might have overlapping functionality, so it doesn't reach the highest score.

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 description provides no guidance on when to use this tool versus alternatives. With siblings like 'tv_airing_today', 'trending_tv_day', and 'trending_tv_week', there's no indication of how this tool differs in scope or timing, leaving the agent to guess based on the name alone.

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