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 bears full responsibility. It specifies that only published posts are returned and lists output fields, but it does not mention ordering (e.g., by date descending), recency definition, or concurrency/rate limits. It is adequate but not highly informative.
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 communicates the tool's purpose and output upfront. No wasted words.
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?
Without an output schema, the description covers return fields (title, excerpt, etc.). It could specify ordering or recency threshold, but for a simple list tool, it is sufficiently complete for an agent to understand the result shape and filter parameters.
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%; both parameters have clear descriptions (limit with default/max, category as case-insensitive substring). The tool description adds no further parameter context beyond the schema, so it meets 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?
The description clearly states that the tool lists recent published blog posts for a Wix Blog site and enumerates the return fields (title, excerpt, author, etc.). It differentiates from sibling tools that handle other entities like products, events, or booking services.
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 retrieving published blog posts with optional filtering; however, it does not explicitly state when to use this tool versus alternatives. Since sibling tools handle different domains, the purpose is clear enough that an agent can infer appropriate 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.
Every tool has a clearly distinct purpose, with detailed descriptions that prevent ambiguity. Overlaps like create_booking vs request_reservation are clarified by domain (appointments vs restaurant) and mechanics.
All tool names follow a consistent verb_noun pattern (e.g., create_booking, list_events, search_places). The same conjugation style (snake_case) is used throughout, with no mixing of conventions.
At 28 tools, the set is slightly larger than the typical well-scoped range (3-15), but each tool corresponds to a distinct feature of the neighborhood directory, making the count reasonable for the breadth of functionality.
The tool surface covers all major user-facing actions: searching, browsing, booking, purchasing, and retrieving information. No obvious gaps exist for the stated purpose of a neighborhood directory.
