Fetch up to 21 current article headlines from a specific Daily Maverick section using its category slug.
Get headlines from one Daily Maverick section. Returns up to 21 current article cards from the public category JSON endpoint. Use dailymaverick-sections to discover valid slugs.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Daily Maverick category slug |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full behavioral burden, and it does deliver: it discloses the 'up to 21' result cap and names the public category JSON endpoint, implying no auth and a read-only fetch. It omits any rate-limit, error, or freshness/pagination caveats, but the essentials are present.
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?
Three short sentences, zero filler, and the scope and result shape are front-loaded before the discovery hint. Every sentence carries information an agent needs.
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 single-enum-parameter tool with no output schema, the description covers what it returns (up to 21 article cards), the source, and how to satisfy the parameter. Field-level detail of the returned cards is missing, but that is a minor gap for a headlines endpoint.
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 100% with an enum of 51 slugs, so the baseline is 3; the description adds value by pointing to dailymaverick-sections as the way to obtain valid slug values. It does not explain whether the enum is exhaustive or whether slugs are case-sensitive.
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 headlines') and resource ('Daily Maverick section') with an explicit scope ('one section'), so the agent knows exactly what the tool returns. It does not differentiate from the sibling dailymaverick_news, but the core purpose is unambiguous.
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?
Explicitly tells the agent to call dailymaverick-sections first to discover valid slugs, which is actionable prerequisite guidance. It lacks a clear statement of when to prefer this over dailymaverick_news or dailymaverick_article, so it stops short of full when/when-not coverage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.