Fetch current headlines from a selected National Post section. Provide a section slug to receive fresh article headlines in structured JSON format.
Get National Post section headlines. Returns fresh headlines from one public National Post section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | National Post section 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 provided, the description carries the full burden of behavioral disclosure. It does state that the tool is public and returns 'fresh' headlines, which conveys access level and recency. It lacks details on response format, limits, or invalid-section behavior, but what is present is accurate and useful.
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 short sentences with the action front-loaded and zero filler. Every clause contributes either the resource, the scope, or the freshness trait without repeating schema content.
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-parameter tool, the definition is close to sufficient, but with no output schema, the agent is not told what the response contains beyond 'headlines' or how errors or empty sections are handled. The missing output and error behavior details are a meaningful gap.
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 description coverage is 100%, with the lone 'section' parameter already documented as a slug backed by a detailed enum. The description's 'one public National Post section' adds a small amount of context but no meaningful syntax or format detail beyond what the schema provides, so the baseline score of 3 applies.
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 opens with a specific verb-resource pair, 'Get National Post section headlines,' which clearly states the action and target. The second sentence adds scope—'one public National Post section'—but it does not explicitly differentiate this tool from siblings like nationalpost_news or nationalpost_sections.
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 'one public National Post section' implies the caller must supply a section, and the required enum parameter reinforces that. However, no alternatives or when-to-use guidance are provided, so an agent must infer when this tool is preferable to other headline or section tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.