List available contact/signup forms on this site (Wix Forms). Returns form name, ID, and field definitions (label, type, required). Use before submit_form to discover which fields to fill.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses return values (name, ID, field definitions) and implies read-only behavior. It doesn't mention rate limits or permissions, but for a simple list tool this is adequate.
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, front-loaded with purpose. Efficient but slightly dense; could be split for readability, but no waste.
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 tool with no parameters and no output schema, the description is complete: explains what it does, what it returns, and when to use it in relation to a sibling tool.
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?
There are zero parameters, so schema coverage is 100%. Baseline is 4 as per instructions; description adds no extra param info, but none needed.
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 it lists contact/signup forms on Wix Forms, specifying the verb 'List' and resource 'forms'. It distinguishes itself from sibling 'submit_form' by indicating it's a preparatory step.
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 advises to use this tool before 'submit_form' to discover fields to fill, providing clear context and alternative.
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 and action. Even similar operations like create_booking, request_reservation, reserve_event_tickets, and rsvp_event are clearly differentiated by their descriptions and the entities they handle (bookable services, restaurant tables, paid events, free events). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern with lowercase and underscores (e.g., create_booking, get_availability, list_events, search_places). This uniform convention makes the tool set predictable and easy for an agent to understand and select from.
With 28 tools, the set is relatively large, exceeding the typical well-scoped range of 3-15. While each tool serves a specific purpose within the neighborhood directory domain, the count feels heavy and may overwhelm simple use cases. A reduction or grouping could improve coherence.
The tool set covers a broad range of user-facing operations for a neighborhood directory: searching places, browsing menus, booking services, reserving tables and event tickets, listing products and events, retrieving reviews and FAQs, and submitting forms. Minor gaps exist (e.g., no cancellation or create_review tool), but the core workflows are well-supported.
