Fetch headlines for a specified SFGate section from one public RSS feed, returning structured JSON for news monitoring or display.
Get SFGate section headlines. Returns fresh headlines from one SFGATE public RSS feed.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | SFGate 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 adds some behavioral context (fresh headlines from an RSS feed) but does not disclose output structure, limits, or explicitly confirm read-only behavior. It provides minimal value beyond the basic purpose.
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 concise: two sentences with the action front-loaded. There is no wasted wording, though it could be improved by mentioning alternatives or output details.
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?
Without an output schema, the description is incomplete. It does not specify the format of returned headlines (titles only? with URLs? metadata?), the maximum count, or any pagination. An agent may not know what to expect from the call result.
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 input schema already fully describes the single parameter with an enum and a description, so schema coverage is 100%. The description adds no additional meaning about the parameter, so the baseline score of 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 clearly states the tool retrieves SFGate section headlines, which distinguishes it from article/author/sections tools. The resource is specific (section headlines) and the action verb is clear. However, it does not explicitly contrast with sfgate_news, which could be a sibling alternative.
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 provides no guidance on when to use this tool versus alternatives like sfgate_news or sfgate_sections. It only states what it does without context on selection criteria or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.