latest_storiesReturn a bounded newest-first slice of the validated public editorial feed, retaining source, evidence, publication, and release fields.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No |
| Name | Required | Description | Default |
|---|---|---|---|
| feed | Yes | ||
| count | Yes | ||
| schema | Yes | ||
| release | Yes | ||
| stories | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds useful context: the feed is 'validated', 'public', the ordering is newest-first, and specific fields are retained. This goes beyond the annotations without contradicting them.
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, front-loaded sentence with no filler. It efficiently conveys the resource, ordering, bound, and retained fields without redundancy.
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?
Given the tool's simplicity (one parameter, no nested objects, and an output schema), the description covers the essential behavioral aspects: what is returned, the ordering, the bounded nature, and the feed type. The output schema handles return details, and annotations cover safety. Nothing critical is missing for an agent to invoke it correctly.
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 description coverage is 0%, so the description must compensate. The word 'bounded' hints at the limit parameter but does not explicitly explain that 'limit' controls the number of items returned. Since there is only one parameter and it is named 'limit' with clear constraints (default 10, max 20, min 1), the schema provides most of the meaning, but the description could have linked 'bounded' to the parameter more directly.
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 uses a specific verb ('Return') and a specific resource ('validated public editorial feed'), and clearly characterizes the result as a bounded newest-first slice that retains specific fields. This distinguishes it from sibling tools like search_stories or get_story, though it doesn't name them.
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 clearly indicates this tool returns the latest stories from a validated public feed, which provides clear context for when to use it. However, it does not explicitly contrast with alternatives like search_stories for targeted queries, so some guidance on when-not-to-use is missing.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: health check, exact story retrieval, latest feed listing, capability introspection, and search. There is no significant overlap that would cause misselection, as get_story is by exact ID, search_stories is flexible querying, and latest_stories is a chronological feed.
Names are all lowercase with underscores, and most follow a verb_noun pattern (get_health, get_story, list_capabilities, search_stories). latest_stories is the outlier, using an adjective-noun form, which is a minor deviation but still readable and predictable.
Five tools is well within the ideal 3-15 range and covers the server's stated purpose of editorial discovery without redundancy or bloat. Each tool earns its place for a focused read-only surface.
The toolset covers core discovery workflows—retrieval by ID, listing, search, and capabilities. Minor gaps include lack of explicit pagination control for latest_stories (though 'bounded slice' implies some limit) and no filtering endpoint beyond search, but these are workable.