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 bears full responsibility. It indicates a read operation but does not disclose ordering, pagination, authentication requirements, or any side effects. Only 'recent published' scope is noted.
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?
A single sentence that front-loads the main purpose and is free of redundant information. Every part is essential.
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?
For a simple list tool with two optional parameters and no output schema, the description is mostly complete. It specifies return fields and scope, but lacks mention of default ordering (e.g., by date). Minor gaps.
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% (both parameters have descriptions). The description adds no extra meaning beyond the schema; it does not explain parameter behavior or provide examples.
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 explicitly states 'List recent published blog posts for this site (Wix Blog)' with a specific verb and resource, and lists returned fields, distinguishing it from sibling tools like list_events or list_faqs.
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 guidance is provided on when to use this tool versus alternatives. There is no mention of when not to use it or comparison to other list 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 operation: bookings, restaurants, events, forms, etc. Even similar actions like create_booking and request_reservation are clearly differentiated by domain and description.
Tools follow a consistent verb_noun pattern (e.g., create_booking, get_availability, list_blog_posts). Collection retrieval uses list_ while single item uses get_, which is a standard and clear convention.
28 tools is on the upper end, but each serves a distinct function for a comprehensive neighborhood directory (places, events, booking, forms, etc.). No obvious bloat given the scope.
The tool surface covers all major user intents for a local directory: searching places, getting menus, booking services, viewing events, submitting forms, etc. No critical gaps are apparent.