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?
Without annotations, the description provides minimal behavioral context beyond the basic read operation. It does not mention safety profile, pagination behavior, or auth requirements, leaving important details unspecified.
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 concise, front-loading the main action, and includes a separate sentence for return values. No superfluous words; every sentence adds value.
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 no output schema, the description adequately lists the returned fields. It could be improved by mentioning that posts are returned in chronological order and whether an ID is included for further operations.
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%, so both parameters are already described. The description adds return field information but does not enhance parameter meaning. Baseline score of 3 is appropriate.
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 action ('list'), the resource ('recent published blog posts'), and the context ('for this site (Wix Blog)'). It effectively distinguishes itself from sibling tools which target different entities (e.g., products, events).
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?
While no explicit alternatives or exclusions are provided, the description clearly indicates that this tool is for listing blog posts. In the absence of other blog-related tools, the usage context is clear.
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 action, with clear boundaries between similar operations (e.g., create_booking vs request_reservation vs reserve_event_tickets). Descriptions provide enough context to avoid confusion.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., create_booking, get_availability, list_events. No mixing of styles or ambiguous verbs.
28 tools is slightly above average but appropriate for a multi-feature neighborhood directory covering bookings, events, movies, menus, forms, etc. Each tool serves a distinct purpose, justifying the count.
The tool set covers most expected operations for a directory site: search, details, reviews, booking, events, menus, blog, FAQ, forms, etc. Minor gaps like cancellation or user booking history are acceptable given the domain scope.