Fetch Al Jazeera section headlines by topic slug. Returns the newest public stories from a specific section archive page.
Get Al Jazeera section headlines. Returns the newest public Al Jazeera stories from one section archive page. topic is a section slug; use aljazeera-categories for the current value space.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | Al Jazeera section slug |
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses that results are the newest public stories from one section archive page. It does not mention return shape, pagination, or limits, and there is no output schema to fill that gap.
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 no filler. The primary action is front-loaded, the return behavior is stated compactly, and the parameter guidance is attached cleanly without redundancy.
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 one-parameter read-only headline fetcher, the core facts are present: what it returns, the section scope, and where to find valid slug values. It is only slightly incomplete because the response payload format and pagination are unspecified and no output schema exists.
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 documents topic as 'Al Jazeera section slug' with 100% coverage, so the baseline is 3. The description adds meaningful extra guidance by telling agents to use aljazeera-categories for the current value space, which reduces guesswork about valid slugs.
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 action and resource: 'Get Al Jazeera section headlines' and further narrows it to 'one section archive page', making it distinct from generic all-headline tools. The reference to aljazeera-categories for the value space reinforces its section-scoped purpose.
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 implies when to use the tool: when an agent needs Al Jazeera headlines for a specific section. It also gives a useful pointer to aljazeera-categories for valid section slugs. However, it never explicitly contrasts this tool with siblings like aljazeera_headlines or aljazeera_news, and it offers no when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.