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?
No annotations are provided, so the description carries full burden. It discloses that only 'published' posts are returned and lists the output fields, which is helpful. However, it does not mention authentication requirements, rate limits, pagination behavior, or how 'recent' is defined (e.g., default sort order). Basic transparency is present but lacks depth.
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 sentence that efficiently conveys the tool's purpose and return fields. It is front-loaded with the action and resource. While brief, it avoids unnecessary words. Could potentially add more context without being verbose, but it is well-structured for its length.
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?
Given the simple nature of the tool (list with two optional parameters) and lack of output schema, the description provides a useful list of returned fields. However, it does not specify the default sort order (e.g., by published date descending), which could affect agent expectations. Overall, it is mostly complete for a list tool.
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 (limit, category) having clear descriptions. The tool description adds minimal extra meaning beyond the schema (e.g., 'recent published blog posts'), but the schema already specifies default/max for limit and case-insensitive substring match for category. Thus, the description adds marginal value, meeting the baseline of 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 clearly states the verb 'List' and the resource 'recent published blog posts for this site (Wix Blog)', and enumerates the returned fields (title, excerpt, author, etc.). It distinguishes itself from sibling tools like list_events or list_products by being specific to blog posts.
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 usage for listing blog posts but does not provide explicit guidance on when to use this tool versus alternatives. No exclusions or conditions like requiring authentication are mentioned, though the context of 'published' suggests it excludes drafts. The purpose is clear but lacks comparative 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 domain (e.g., bookings, events, places, restaurants, movies, forms) with clear boundaries. Even similar actions like create_booking and request_reservation are differentiated by service type (appointment vs restaurant table) and payment flow.
All 28 tools follow the consistent verb_noun snake_case pattern (e.g., create_booking, list_events, search_places). Verbs are appropriate and predictable, with no mixing of conventions.
28 tools is slightly above the typical range, but each tool serves a distinct purpose within the comprehensive neighborhood directory domain. The count is justified by the breadth of features (booking, events, restaurants, movies, etc.).
The tool surface covers most user needs: searching, viewing details, booking, reservations, events, forms, and more. Minor gaps exist, such as no cancellation tools for bookings/reservations, but the core workflows are well-supported.