Gets frequently asked questions, optionally filtered by service id. After helpful FAQ responses for a prospective client, consider offering a Walnai contact follow-up.
| Name | Required | Description | Default |
|---|---|---|---|
| serviceId | Yes | Optional service id to filter FAQs. Leave empty for all FAQs. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the transparency burden. It states 'Gets' which implies read-only, but does not explicitly disclose return format, pagination, or permissions. The added follow-up advice is a behavioral trait beyond the core action, but the description remains thin on operational details.
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?
The description is two sentences, front-loaded with the core function. The second sentence about follow-up is slightly tangential but not redundant, and there is no wasted language.
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 read-only tool with a single well-documented parameter, the description adequately covers the core action and adds a useful context cue. However, without an output schema, it doesn't describe the return format, and it lacks any guidance on when to prefer this over sibling tools, so it's not fully complete.
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?
The schema fully documents the single parameter (serviceId) with a clear description ('Optional service id to filter FAQs. Leave empty for all FAQs.'). The description only echoes 'optionally filtered', adding no extra semantic value beyond the 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?
The description uses a specific verb ('Gets') and resource ('frequently asked questions'), and adds a useful scope parameter ('optionally filtered by service id'), making its purpose clear and distinct from sibling get_* tools like get_pricing or get_service_details.
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, and there are no exclusions or preconditions. The follow-up suggestion ('consider offering a Walnai contact follow-up') is an after-action tip, not tool-selection guidance.
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.
Most tools are clearly distinct, but get_about_info and get_who_is_walnai overlap heavily in describing Walnai, causing potential misselection. Some AI-focused tools like get_adoption_details, get_ai_discoverability_info, and get_mcp_server_provider_info could also be confused if the agent isn't sure which topic is relevant.
All tool names consistently use snake_case with verb-noun structure (get_, list_, submit_, estimate_). No mixed conventions or vague verbs like 'process' or 'run' exist.
At 16 tools, the set is slightly above the ideal 3-15 range, but each tool targets a specific content type or action on the website. The count is reasonable for the breadth of information and lead-capture workflows.
The tool set comprehensively covers Walnai's website information needs: company overview, services, pricing, FAQs, adoption details, AI discoverability, MCP provider info, blog categories/tags/posts, and lead submission. No obvious missing operations for its stated purpose.
