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?
With no annotations, the description provides basic behavioral info (lists published posts, return fields) but lacks details on sorting, pagination, or performance implications. It doesn't contradict any annotations.
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 concise sentence that front-loads the action and resource. Every part adds value, with no unnecessary 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?
Given the tool's simplicity (2 optional parameters, no output schema), the description adequately covers purpose and return fields. It is sufficiently complete 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 description coverage is 100%, so baseline is 3. The description does not add extra meaning to the parameters beyond what the schema already provides.
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 resource 'recent published blog posts for this site (Wix Blog)'. It also lists the specific return fields, distinguishing it from sibling tools like list_events or list_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?
The description implies usage when blog post data is needed, but does not explicitly state when to use or not use this tool, nor does it mention alternatives among the many 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 and domain, with clear descriptions preventing confusion. Similar tools like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are differentiated by service type and workflow.
All tools follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_categories), ensuring predictability and ease of use for agents.
With 28 tools, the set is fairly large but appropriate for a comprehensive neighborhood directory covering multiple domains (places, events, booking, store, forms, etc.). Each tool serves a distinct purpose without redundancy.
The tool surface covers the full lifecycle of common user needs: search and discovery, detailed info, reservations, purchases, and interactions (forms, FAQs). No obvious gaps for the described purpose of a neighborhood directory.