search_articlesSearch Psychiatry for Teens's editorial corpus by query. Returns title, slug, summary, and URL for matching articles.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Alternate parameter name for `query`. | |
| limit | No | Max results (default 10, max 50). | |
| query | Yes | Free-text search query. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the read-only safety is covered. The description adds meaningful behavioral context by scoping to the editorial corpus and explicitly listing the return fields (title, slug, summary, URL). It doesn't cover ordering or rate limits, but those are not critical for a read-only search.
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 action, and contains no filler words. It precisely states what the tool does and what it returns, earning every word.
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?
The description gives the essential context: what is searched, the scope, and the return structure. It doesn't mention default limit or the q alias, but these are fully documented in the schema. For a read-only search tool without an output schema, this is sufficient 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 100% across all three parameters (q, limit, query). The description does not add any parameter-level semantics beyond what the schema already provides, so the appropriate baseline is 3.
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 the specific verb 'Search' with a clear resource ('Psychiatry for Teens's editorial corpus') and states what the return fields are (title, slug, summary, URL). This clearly distinguishes it from sibling tools like list_articles, which would list all articles without a query.
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 implies this tool should be used when you need to find articles matching a query. However, it does not explicitly mention alternatives or exclusions, so it misses the 'when-not-to-use' guidance. Still, the context is clear enough for an agent to select it over listing tools.
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: article discovery (list, search), retrieval (get), citation (cite), site identity (microsite info), and crisis support. No two tools overlap, and the descriptions reinforce their uniqueness.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., cite_article, list_articles, get_crisis_resources). The naming is uniform and predictable.
Six tools is well-scoped for a read-only article library. It covers discovery, retrieval, citation, site context, and crisis support without unnecessary bloat.
The domain is fully covered: users can search, list, retrieve full articles, generate citations, access site information, and get crisis resources. No critical operations are missing, and the set forms a complete workflow.