Get CBC News sections for headlines: national desks, regional newsrooms, and CBC Sports feeds.
Get CBC News sections. Returns the CBC News sections accepted by the headlines endpoint: national desks, regional newsrooms, and CBC Sports feeds.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 behavioral burden. It discloses that the tool returns section names, specifies the meaningful categories, and ties the output to the headlines endpoint. It omits return format details and note that this is a read-only call, but for a zero-parameter metadata lookup the provided behavior is clear and adequate.
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?
The description is two sentences long, front-loads the purpose, and uses the second sentence only to add scoping and content details. Every word earns its place; no filler.
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 parameterless list tool with no output schema, the description is complete: an agent knows what action to take, what it will receive, and how the result relates to cbc_headlines. Nothing necessary for correct invocation is missing.
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 has zero parameters and 100% schema coverage, so the description need not add parameter details. The baseline of 4 applies; there are no undocumented inputs to compensate for.
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 states a specific verb and resource: 'Get CBC News sections.' It further distinguishes itself from cbc_headlines and other *_sections tools by clarifying it returns sections accepted by the headlines endpoint, enumerating the categories: national desks, regional newsrooms, and CBC Sports feeds.
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 phrase 'accepted by the headlines endpoint' gives clear context that this tool is a lookup for values to use with cbc_headlines. It does not explicitly state 'use this before calling cbc_headlines' or list when not to use it, but the relationship is strongly implied and sufficient.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.