List recent published blog posts for this site (Wix Blog). Returns title, excerpt, author, published date, reading time, categories, and the post URL.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max posts to return (default 10, max 50). | |
| category | No | Filter by category label. Case-insensitive substring match. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that it returns recent published posts with specified fields, providing some behavioral context. However, lacks details on sorting order, pagination beyond limit, authentication needs, or side effects. No annotations present to supplement.
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?
Single sentence efficiently conveys purpose and return fields. Slightly dense but front-loaded and earns its place; could be split for readability.
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?
In absence of output schema, describes return fields adequately. Covers key aspects but omits potential error scenarios or advanced behaviors like cursor-based pagination.
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 detailed parameter descriptions. The description adds no extra meaning beyond what the schema already provides for parameters, meeting the baseline.
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?
Clearly describes the tool as listing recent published blog posts for the Wix Blog, with specific verb 'List' and resource 'blog posts'. Distinguishes from sibling list tools that cover other entities like events or products.
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?
No explicit guidance on when to use this tool versus alternatives. While the context implies use for blog posts, there is no mention of prerequisites, when not to use it, or comparison to sibling 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 targets a distinct action on a specific resource (e.g., create_booking vs create_checkout vs reserve_event_tickets). Descriptions clearly differentiate purposes, and no two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_availability, list_categories, search_dishes). Verbs like get, list, create, request, rsvp are used uniformly, making the set predictable.
28 tools is above the typical 3-15 range, but the server covers a broad domain (places, events, movies, booking, store, etc.). Each tool serves a clear purpose, so the count is justified for the scope.
The tool surface is extensive, covering searching, details, reviews, booking, events, menus, etc. Minor gaps exist (e.g., no cancel/update operations), but they are likely intentional given the user-facing nature of the server.
