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, so description carries full burden. It mentions submission on behalf of user and returns submissionId, but lacks details on side effects, permissions, or error conditions. Adequate but could be more transparent.
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 filler. Essential information is front-loaded: action, prerequisite, return value. 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 2 required params, high schema coverage, and no output schema, the description covers the necessary steps (prerequisite, return) and is complete for the tool's simplicity.
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%, and parameter descriptions are clear. The description adds usage context (e.g., use list_forms to get keys) but does not significantly enhance meaning beyond schema. Baseline 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 ('Submit a form'), the resource ('Wix Forms'), and the prerequisite step. It distinguishes from siblings like list_forms by indicating it is the next step after obtaining form data.
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 formId and field keys, providing clear usage context. Does not explicitly list alternatives or when not to use, but the guidance is sufficient.
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.