Retrieve current CNET headlines for any section. Select a topic slug to receive structured JSON headlines from the public feed.
Get CNET section headlines. Returns fresh CNET headlines from one public topic feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | CNET topic slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses that the tool returns fresh headlines from a public feed, implying a read-only operation with no authentication. However, it omits details like pagination, rate limits, or output structure, which is acceptable for a simple tool but not exhaustive.
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 zero waste, front-loaded with the main purpose and source. Every word 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 simple list tool with one parameter and no output schema, the description covers the essentials: what it returns (headlines) and its source (public topic feed). It could mention output format or limits, but nothing critical is missing for basic usage.
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 fully documents the single parameter 'section' with an enum and description ('CNET topic slug'). The description adds no additional parameter semantics. Since schema coverage is 100%, a baseline of 3 is appropriate.
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 (Get) and resource (CNET section headlines), and clarifies it comes from a single public topic feed. This is clear enough to distinguish from other CNET tools like cnet_news or cnet_sections, though it doesn't explicitly name alternatives.
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?
Implies usage for section-specific headlines but provides no explicit when-to-use guidance or contrast with sibling tools like cnet_news or other headline tools. No exclusions or alternative routing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.