Fetch fresh headlines from a public Fortune section by providing its slug. Returns clean, structured JSON ready for integration.
Get Fortune section headlines. Returns fresh headlines from one public Fortune section.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Fortune 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 full burden. It only mentions freshness and public sections, but does not disclose pagination, error behavior, or return structure. For a simple read tool that's minimal, but it's still thin.
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 core purpose first. No waste.
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?
The tool is simple with one param and no output schema, but the description doesn't describe the shape of the returned headlines (just 'headlines'). It might be sufficient given the simplicity, but could mention whether it returns titles and URLs, or just a list.
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 schema already documents the section parameter as 'Fortune section slug' with a full enum, so coverage is 100%. The description adds only 'public' which is minor; it doesn't explain slug format or any special cases.
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 the specific resource ('Fortune section headlines') and the verb 'Get', clearly distinguishing it from sibling tools like fortune_article or fortune_author. It also clarifies the scope ('from one public Fortune section').
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 (when you need headlines from a specific Fortune section) but does not explicitly contrast with alternatives like fortune_article or fortune_news. It provides no 'when not to use' guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.