Get current headlines from a Philstar section page by slug, because no crawlable feeds exist.
Get Philstar section headlines. Returns the current headlines from the first page of one public Philstar section page (Philstar publishes no crawlable feeds, so this reads the section page itself).
| Name | Required | Description | Default |
|---|---|---|---|
| section | Yes | Philstar 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 provided, the description carries the full burden. It transparently discloses the source ('public Philstar section page'), freshness ('current headlines'), and scope ('first page'), and explains why it reads the page itself. However, it does not disclose output structure, pagination behavior, or potential operational quirks.
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 a single focused sentence plus a short parenthetical. It leads with the action and resource, then adds the essential scoping detail and a relevant explanatory note. No filler or redundant phrasing.
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 tool with no output schema and no annotations, the description adequately covers what is returned, from where, and why the mechanism is page scraping. It could mention the return format explicitly, but the word 'headlines' strongly implies a list of headline items, so the gap is minor.
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 provides 100% parameter coverage with the enum description 'Philstar section slug', so the description adds little beyond context. It reinforces that the section refers to a section page, but does not explain slug formatting or mapping—though the enum values themselves make this mostly unnecessary.
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 starts with 'Get Philstar section headlines', a specific verb and resource. It clarifies the scope by stating it returns 'current headlines from the first page of one public Philstar section page', which distinguishes it from article, news, and sections tools without naming siblings explicitly.
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 its usage context — fetching current headlines for a particular section — but does not state when to prefer this tool over philstar_article, philstar_news, or philstar_sections. The parenthetical explains the implementation mechanism (page scraping because no feeds exist) but not the selection criteria among related tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.