Fetch Chicago Tribune headlines for a chosen section. Specify a section slug to receive fresh headlines from that public page.
Get Chicago Tribune section headlines. Returns fresh headlines from one public Chicago Tribune section page.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Chicago Tribune 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, the description carries the full burden. It usefully discloses that headlines are 'fresh' (currently fetched) and come from a 'public' page (implying no auth), but it does not mention output structure, headline count, pagination, or behavior on invalid section slugs.
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 tight sentences with no fluff. The operation and key behavioral notes are front-loaded, and every word earns its place.
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 tool with no output schema, the description covers the core operation and scope, but it lacks any indication of the return format (e.g., list of headline objects with titles/links/dates), which an agent would need to use the results correctly.
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% and the enum fully documents valid section slugs. The tool description adds only the vague connection between 'section' and a 'section page,' which is marginal beyond what the schema already provides, so baseline 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 uses a specific verb ('Get') and resource ('Chicago Tribune section headlines'), and clarifies per-section scope with 'one public Chicago Tribune section page.' It distinguishes itself from sibling article/author tools by focusing on headlines, though it doesn't name an alternative outright.
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 'section headlines' and 'one public Chicago Tribune section page' imply the tool is for fetching headlines for a single section using the section slug, but there is no explicit when-to-use guidance, exclusions, or comparison with alternatives like chicagotribune_news or chicagotribune_sections.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.