Submit a form on behalf of the user (Wix Forms). Call list_forms first to get the formId and field keys. Returns a submissionId on success.
| Name | Required | Description | Default |
|---|---|---|---|
| fields | Yes | Key-value pairs matching the field keys from list_forms. Example: { "field_1": "João", "field_2": "joao@email.com" } | |
| formId | Yes | Form ID from list_forms. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations present, so description carries full burden. It discloses the return value (submissionId) but does not mention side effects (e.g., email notifications), permissions needed, or consequences of submission. Adequate but not comprehensive.
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?
Two sentences, no wasted words. Critical information is front-loaded: action, prerequisite, return value. Extremely concise yet informative.
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 2 parameters, full schema coverage, and no output schema, the description adequately explains the tool's purpose and usage. Mentions the return value (submissionId) and prerequisite tool. Could optionally detail response schema, but not required.
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%, and description adds value by explaining where to get the formId and field keys, plus provides an example for the fields parameter. Goes beyond raw schema.
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?
Description clearly states it submits a form on behalf of the user for Wix Forms, with a specific verb ('submit') and resource. Differentiates from sibling tools like list_forms by mentioning it as a prerequisite.
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?
Explicitly instructs to call list_forms first to obtain the formId and field keys, providing clear when-to-use guidance. Lacks explicit when-not-to-use or alternatives, but the prerequisite is well-stated.
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 has a clearly distinct purpose, even among similar actions like booking, reservation, and ticket purchase—their descriptions clarify the domain and flow. No two tools could reasonably be confused.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_booking, get_availability, list_blog_posts). There are no deviations or mixed conventions.
At 28 tools, the surface is larger than ideal for a single server, but each tool covers a distinct feature of the neighborhood directory (bookings, events, store, etc.). It borders on heavy but is still manageable for an agent.
The tool set covers the full lifecycle of browsing and acting on a neighborhood directory: search, details, reviews, menus, events, booking, reservations, store, loyalty, and more. No obvious gaps exist for the intended use case.