Fetches the newest Rappler top stories across all sections, returning each article's title, URL, summary, publication time, author, and lead image.
Get Rappler top stories. Returns the newest Rappler stories across all sections. Takes no parameters. Each item has its title, canonical article URL, a short summary, publication time, author byline and lead image.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.17.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full burden. It usefully discloses the per-item payload (title, canonical URL, summary, publication time, byline, lead image), which is genuine behavioral value, but it omits read-only safety framing, result count/limit, and pagination or freshness behavior.
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?
Three short sentences, front-loaded with the action and scope, with no filler. The return-field list is compact and directly useful.
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 parameterless headline-list tool with no output schema, the description covers purpose and returned fields adequately. The remaining gap is that it gives no sense of how many stories come back or how it relates to rappler_headlines.
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 tool takes zero parameters, so the baseline is 4. The description correctly and explicitly states 'takes no parameters', which is the only parameter-level fact an agent needs.
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+resource: fetches Rappler top stories, and clarifies the scope ('newest stories across all sections', 'takes no parameters'). It does not differentiate itself from the close sibling rappler_headlines, so an agent cannot know from this text alone whether the two overlap or how they differ.
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 says what it returns but gives no when-to-use guidance: no indication of when to prefer this over rappler_headlines, rappler_sections, or rappler_article, and no mention of ordering, currency, or refresh behavior.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.