cnn_headlines

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

With no annotations present, the description carries the behavioral burden. It discloses that the tool returns a 'current' headline stream for one section and enumerates the returned fields (title, URL, description, publication time, and optional image), going beyond the name and schema.

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 with the core information front-loaded and no filler. Every phrase—'current', 'one section', and the returned fields—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?

For a low-complexity tool with one optional parameter and no output schema, the description is complete: it says what is returned, when it is current, and which section is targeted. Additional details like ordering or pagination are not necessary for correct invocation.

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 schema already fully documents the only parameter with allowed values and a default, so the description adds minimal parameter-level meaning. The mention of 'one section' reinforces that the section parameter selects the stream, but this is baseline value given 100% schema 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 opens with 'CNN section headlines' and states it 'Returns the current CNN headline stream for one section', identifying a specific verb, resource, and scope. This clearly differentiates it from sibling CNN tools like cnn_article and cnn_live_story.

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 clearly conveys the intended use: fetching current CNN headlines for a chosen section, so an agent can select it when a user asks for CNN headlines. It does not explicitly name alternatives or exclusions, but the single-section framing provides enough context.

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