Returns all published stories for a given category (e.g., foundation, sense, focus, discovery, delivery). The input must be a single category string.
| Name | Required | Description | Default |
|---|---|---|---|
| category | Yes | The category to fetch stories for. Must be one of: foundation, sense, discover, focus, deliver. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must convey behavioral traits. It states 'published' as a filter and implies a read-only operation, but does not disclose pagination, response size limits, or error behavior for invalid categories. It adds some value but leaves notable gaps.
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 two sentences, front-loaded with the primary action, and every word serves a purpose. It is highly concise with no redundant information.
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, the output schema presence, and full schema coverage, the description covers the essential information. It could be slightly more complete by not naming the input and clarifying the exact enum values, but overall it is sufficient for an agent to invoke the tool 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?
The schema provides 100% coverage of the category parameter with an enum and description, so the baseline is 3. The description adds examples and emphasizes 'single category string,' but those examples are slightly inaccurate relative to the schema, and no additional meaning is provided beyond what the schema already contains.
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 returns all published stories for a given category, using the verb 'returns' with a specific resource and filter. However, the example categories listed ('discovery', 'delivery') do not exactly match the enum values in the schema ('discover', 'deliver'), introducing minor confusion. It is still distinguishable from siblings like list_stories or get_articles_by_tag.
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 usage for fetching stories by category and states the input must be a single category string, but it does not explicitly mention when to use this tool versus alternatives like list_stories or search_articles. There is no exclusion guidance or when-not-to-use information.
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 clear, distinct purpose: list tools for enumeration, get tools for retrieval by specific identifiers or filters, and search for free-text discovery. The two get_article_details variants are clearly differentiated by slug vs. UUID usage, and get_articles_by_tag vs. search_articles are distinct in their input criteria.
The naming pattern is predominantly consistent with list_* for all-resource retrieval, get_*_by_* for filtered access, and search_* for discovery. Minor deviations include the verbose 'get_article_details_by_slugs' vs. the simpler 'get_articles_by_tag', and a description in search_articles referring to a non-existent 'get_article_by_id' tool.
Eight tools provide a well-scoped surface for a read-only content API covering categories, stories, and articles. The count is neither too sparse nor overwhelming, and each tool contributes a unique retrieval mode.
The tool set covers the essential read operations: listing all entities, fetching by identifiers, filtering by tag or category, and text search. Minor gaps include no direct story-by-slug retrieval and no search across stories, but these are workable via existing tools.
