list_articlesPaginated list of articles from Anxiety in Children. Returns title, slug, summary, and URL.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number (1-indexed). | |
| limit | No | Max results per page (default 30, max 100). |
Changes observed during successful MCP inspections.
Input schema / $schemaPrevious value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"Input schema / $schemaAdded value: +"http://json-schema.org/draft-07/schema#"Input schema / properties / limit / descriptionPrevious value: -"Page size (default 30, max 100)."New value: +"Max results per page (default 30, max 100)."Input schema / properties / limit / maximumAdded value: +100Input schema / properties / limit / minimumAdded value: +1Input schema / properties / limit / typePrevious value: -"number"New value: +"integer"Input schema / properties / page / descriptionPrevious value: -"Page number (default 1)."New value: +"Page number (1-indexed)."Input schema / properties / page / maximumAdded value: +9007199254740991Input schema / properties / page / minimumAdded value: +1Input schema / properties / page / typePrevious value: -"number"New value: +"integer"Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, and the description adds useful behavioral context by specifying pagination and the exact fields returned. This is more than just restating the annotation; it helps the agent know what to expect in the response.
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 short sentences, no fluff, front-loaded with the core action and resource. Every word earns its place.
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 tool is simple, with no output schema, but the description adequately states the return fields. However, it does not hint at the sibling search_articles for filtering or other capabilities, which could lead an agent to misuse this tool for search-like needs.
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%, with both params (page, limit) having descriptions. The description's mention of 'paginated' adds slight context but does not go beyond what the schema already provides. Baseline 3 is appropriate.
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 'list' with a clear resource ('articles from Anxiety in Children') and explicitly states the return fields (title, slug, summary, URL). This clearly distinguishes it from siblings like get_article (single article) and search_articles (searching).
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 is for paginated browsing of articles, but it does not explicitly mention when to use it over alternatives like search_articles. There are no exclusions or alternative references, but the context is clear enough for basic use.
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.