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

Annotations already declare readOnly/openWorld, so the safety profile is covered. The description adds genuine behavioral context beyond those: no total count is exposed (affecting pagination termination) and foreign sister-site cards are excluded (affecting result composition). It does not mention rate limits, but the added traits are substantive.

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 tight sentences, front-loaded with the core action and followed by operational constraints. No filler; every clause carries information.

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?

Return fields are lightly enumerated even though an output schema exists, so nothing critical is missing. Pagination limits are addressed, making the definition usable end-to-end for a simple one-param list tool.

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 0% — the lone 'page' param has no description — so the description must compensate. It does: '1-based page number' and 'use sequential page values' define indexing base and iteration behavior, which the schema alone does not convey.

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 ('Fetch') and resource ('NDTV-hosted live-blog cards') with explicit scope ('public', 'one page'). The plural 'cards' set clearly distinguishes it from the sibling ndtv_live_blog (single blog) and other ndtv_* article/headline tools.

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?

Gives pagination guidance ('Use sequential page values; NDTV exposes no total count'), which is useful operational context. However, it never states when to choose this over ndtv_live_blog or other siblings, so usage is only implied.

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