Fetch current New Zealand Herald top stories as structured JSON, with titles, URLs, and optional summaries, authors, publication times, and images.
Get NZ Herald top stories. Returns the current New Zealand Herald top stories, with no parameters. Each item has a title and URL, and may include summary, author, publication time and image. Use nzherald-headlines to read one section.
| 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 full burden, and it delivers: it is a parameterless read of current top stories and it enumerates the return shape (title, URL, optional summary/author/publication time/image). It omits any note on caching, freshness, or item counts, which keeps it from a 5.
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 tight sentences: purpose, return shape, then the sibling escape hatch. Nothing is redundant and the scoping statement is front-loaded.
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?
With no output schema, the description compensates by listing the fields each item may contain, and the empty input schema needs no elaboration. It is complete for an agent to call correctly; only minor details like item count or freshness are unaddressed.
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 takes zero parameters and the description explicitly confirms 'with no parameters,' removing any ambiguity about whether filtering or pagination is available. Baseline for a 0-param tool is 4.
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+resource ('Get NZ Herald top stories') and the exact scope ('current New Zealand Herald top stories, with no parameters'), so it is immediately distinguishable from nzherald_headlines, nzherald_sections, and nzherald_article.
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 routes the agent: 'Use nzherald-headlines to read one section,' which draws the line between this aggregate top-stories feed and the per-section sibling. It does not mention the article/author tools, but the primary alternative is named.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.