search_articlesSearch this publication's articles by keyword. Returns the best-matching titles, dates, canonical URLs, and short summaries.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 5, max 20) | |
| query | Yes | Search keywords |
| Name | Required | Description | Default |
|---|---|---|---|
| total | No | ||
| articles | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds useful context about returning best-matching titles, dates, canonical URLs, and summaries, but does not disclose pagination or result-ranking behavior beyond that.
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 concise sentences: the first states the action and scope, the second summarizes the result content. No wasted words and the core purpose is front-loaded.
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 simple read-only search tool with an output schema present, the description is largely sufficient. It could be more complete by clarifying how it differs from the generic 'search' sibling, but nothing essential to calling it is missing.
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%, documenting 'query' and 'limit' fully. The description reinforces the keyword-search behavior but adds little beyond what the schema already provides.
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: 'Search this publication's articles by keyword.' The return-value summary further clarifies the tool's focus, though it does not explicitly differentiate from the sibling tool 'search.'
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 context is implied: use this when you need keyword search over articles. However, no explicit guidance is given about when to prefer search_articles over sibling tools like 'search' or 'list_recent_articles.'
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 primary role, but search and search_articles overlap for keyword queries, and fetch and get_article both retrieve full text by different identifiers. Descriptions help distinguish them, but an agent could still select the wrong tool without careful attention.
Most tools use verb-led names like fetch, get_article, list_recent_articles, and search, but popular_content breaks the pattern as a noun phrase. The pairings of fetch/get_article and search/search_articles also create inconsistent specificity across similar operations.
Six tools is a well-scoped set for a content retrieval gateway, covering discovery and retrieval without padding. Each tool earns its place and supports a coherent read-only workflow.
The surface covers searching, browsing recent and popular content, and fetching full text through two paths. Minor gaps remain, such as no direct URL-based fetch and no explicit way to get full text from search_articles results without extracting a slug, but agents can work around these.