Fetch recent Android Police headlines for a specific section from 18 verified RSS feeds, so you can monitor targeted news without browsing each feed.
Get Android Police section headlines. Returns recent headlines from one of the 18 live-verified primary navigation RSS feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Android Police section slug |
Changes observed during successful MCP inspections.
v1.17.9Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. It usefully discloses the data source ('primary navigation RSS feeds') and that 18 feeds are live-verified, which hints at enum validity and freshness, but says nothing about read-only safety, rate limits, auth, or ordering.
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, purpose front-loaded, with the source detail as supporting context. Efficient, though the 'live-verified primary navigation' phrasing is denser than it needs to be.
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 read-only headline tool with no output schema or annotations, the description covers purpose and source adequately but omits what a returned headline contains (title, link, timestamp) and any ordering or count expectations.
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 coverage is 100% and the single param has an exhaustive 18-value enum, so the schema does the heavy lifting. The description adds only the modest clue that the enum corresponds to primary navigation sections; no format or alias guidance beyond that.
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?
States a specific verb and resource ('Get Android Police section headlines') and reinforces scope with the section-feed framing. However, it does not distinguish itself from close siblings like androidpolice_news or androidpolice_sections, so an agent must infer the difference.
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?
No when-to-use statement, no prerequisites, and no mention of alternatives such as androidpolice_sections for discovering valid section values. Usage is only implied by the verb 'Get'.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.