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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that records carry per-station coverage windows, which is useful context. However, it says nothing about result volume, updates, or what 'current' implies about staleness, so it adds only moderate value beyond the annotations.

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 sentences, zero filler, and the core purpose is front-loaded before the alternative routing. Every clause earns its place.

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?

With annotations covering safety, a zero-parameter schema, and an output schema that documents the return shape, the description needs only to state the purpose and routing – which it does. Minor residual gap is that it never says how large the station list is or how frequently it changes.

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 takes no parameters, so there is no parameter semantics to clarify; the baseline for a zero-parameter tool is 4. The description correctly implies a full enumeration with no filtering input.

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?

States a specific verb and resource ('List current GDELT Television 2.0 AI station records') plus the scope of each record ('each station's coverage window'). It also names the sibling tools it is not, so an agent can distinguish it from gdelt_tv_search and gdelt_tv_stationchart without opening any schema.

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?

Explicitly routes to two alternatives: gdelt_tv_search when you need to find matching stations and gdelt_tv_stationchart for volume charts. That tells the agent when to prefer those tools, leaving this one as the enumeration path. It stops short of stating an explicit 'when not to use' or any prerequisites, so it's a notch below the top.

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