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 useful provenance context (TV 2.0 AI closed captioning, GDELT's own MID taxonomy), but says nothing about whether the list is static or date-scoped, or about result ordering beyond what the schema states.

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?

A single, front-loaded sentence with no filler. It is efficiently sized for a one-parameter reference-lookup tool, though it is arguably too terse given the missing usage guidance.

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?

An output schema exists, so return values need no explanation, and the safety profile is covered by annotations. What is missing is the operational context: what these MID codes are for and how they relate to the other gdelt_tv_* tools, which leaves the agent guessing about when this tool is the right entry point.

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?

Schema coverage is 100% and the single limit parameter is fully documented in the schema (default 100, max 10000, most-frequent-first ordering). The description adds no meaning beyond that, so the baseline of 3 applies.

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 identifies the resource precisely: GDELT's catalog of concept entities (MID codes) as recognized in Television 2.0 AI closed captioning. That is enough to distinguish it from most siblings, though it does not explicitly contrast with the closely related gdelt_tv_visual_entities, which an agent could easily confuse it with.

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 when-to-use guidance, no mention of when this catalog is preferable to gdelt_tv_visual_entities or the gdelt_tv_search/timeline tools, and no hint that the output is a lookup table of codes used elsewhere. The agent must infer the purpose entirely.

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