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 provided; description minimally covers behavior (submission, returns submissionId). Does not disclose authentication needs, side effects beyond submission, or rate limits, but is adequate for a straightforward mutation.
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: first states action and scope, second gives prerequisite and return value. No wasted words, front-loaded with key information.
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?
With 2 parameters fully described in schema and no output schema, the description covers usage flow and return. Lacks error scenarios or duplicate handling, but sufficient for typical use.
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%, but description adds value by explaining how to obtain parameter values (list_forms). Also gives an example format for fields in schema description, enhancing understanding.
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 ('Submit a form on behalf of the user (Wix Forms)') and specifies the resource. It distinguishes from siblings like list_forms by implying a write operation and mentioning return of submissionId.
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?
Provides explicit prerequisite instruction ('Call list_forms first to get the formId and field keys'). Does not mention when not to use or alternatives, but context shows no direct sibling conflict.
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 resource or action: search, get, list, create, submit, etc. Potential overlaps like create_booking vs request_reservation vs reserve_event_tickets are clarified by descriptions distinguishing appointment booking, restaurant table requests, and event ticket holds.
All tool names follow a consistent verb_noun pattern with underscores (e.g., list_services, get_place, create_booking). No mixing of styles, and verbs accurately describe the operation.
28 tools is slightly above typical range but well-justified given the breadth of the site (places, events, movies, food, booking, forms, etc.). Each tool serves a clear purpose without feeling bloated.
Covers major read and action scenarios for a neighborhood directory. Missing update/delete operations for places and bookings, but those are likely not exposed via this API. Minor gaps like canceling reservations are handled externally.