List the most recent posts on the Radixia blog (AI, serverless, open source, cloud). Returns title, slug, date, tags and excerpt for each.
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter by tag slug, e.g. 'ai', 'serverless', 'e-commerce' | |
| limit | No | How many posts to return |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It discloses the return shape (title, slug, date, tags, excerpt) which is useful, but it does not mention any side effects, permissions, rate limits, or whether only published posts are included. The read-only nature is implied by 'List', but not explicitly stated. This is adequate but not rich.
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, well-structured sentence that front-loads the action and resource, with a parenthetical for topics and return fields. Every clause adds value, and there is no wasted text.
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 two optional parameters and no output schema. The description covers the resource, scope, and return fields, which is sufficient for basic usage. Minor gaps include lack of explicit sorting direction (though 'most recent' implies it) and no mention of tag filtering, which is in the schema. Overall, it is complete enough for an agent to use 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 coverage is 100% with both parameters fully described in the schema. The description adds no additional parameter-level context, so it does not go beyond the schema. Baseline 3 is appropriate since the schema does the heavy lifting.
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 verb 'List', the resource 'posts', and the scope 'most recent' on the Radixia blog. It also lists the exact fields returned (title, slug, date, tags, excerpt), distinguishing it from sibling tools like get_post (single post) and search_posts (search-based). This is a specific and unambiguous purpose.
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 when to use this tool (when needing a chronological list of recent posts) but does not explicitly mention alternatives or exclusions. Sibling tools like search_posts and get_post exist, yet the description does not say 'use this instead of X'. It provides clear context but lacks explicit when-not-to-use guidance.
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 targets a distinct resource and action: company info, blog post retrieval, listing, searching, and conference agenda/session retrieval. Potential overlap between search and get tools is mitigated by explicit guidance in descriptions (e.g., get_conference_session tells you to use search first).
Most names follow a clear verb_noun pattern (get_, list_, search_), but 'about_radixia' breaks the pattern as a noun phrase. Overall still readable and consistent in snake_case.
8 tools is well-scoped for a blog + conference content server. Each tool serves a distinct purpose without redundancy or bloat.
The surface covers the read-only content domain comprehensively: blog posts (list, get, search), tags, conference agenda and transcripts (get, search), plus company info. No obvious missing operations for the apparent scope.
