Fetch current headlines from a specified IndieWire section feed, omitting galleries and lists to deliver only text-article headlines.
Get IndieWire section headlines. Returns fresh headlines from one public IndieWire section feed. Gallery and list pages are omitted because they are not text articles.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | IndieWire 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 burden. It discloses that gallery and list pages are omitted because they are not text articles, which is useful behavioral context. However, it doesn't mention whether the tool returns only titles, or also URLs/dates, or any rate limits or freshness details.
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?
The description is two sentences, front-loads the main action, and adds a relevant exclusion note. It's concise and every sentence earns its place, though it could be slightly more structured.
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 simple one-parameter headlines tool, the description is mostly complete. It explains what it returns and what it omits. However, it doesn't specify the output format (e.g., list of headline strings vs. objects with URLs), which an agent might need to know for downstream use.
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%: the only parameter 'section' is described as 'IndieWire section slug' with an enum of valid values. The description adds that it's a 'public IndieWire section feed' but doesn't add much beyond the schema. Baseline 3 is appropriate.
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 states a specific verb ('Get') and resource ('IndieWire section headlines'), and clarifies it returns headlines from one public IndieWire section feed. It doesn't explicitly differentiate from sibling tools like indiewire_news or indiewire_sections, but the name and description make the function clear.
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 usage context: it's for fetching headlines from a specific section feed, and it notes that gallery and list pages are omitted. However, it doesn't explicitly state when to use this tool versus alternatives like indiewire_news or indiewire_sections, nor does it mention any exclusions or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.