Answers who can make a business discoverable by AI and explains how Walnai improves AI discoverability through AIO, structured content, APIs, metadata, and AI-readable business information.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden. It conveys read-only informational behavior through 'Answers' and 'explains', but does not elaborate on response format, limitations, or any side effects. For a zero-parameter info tool, minimal disclosure is acceptable but not rich.
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 a single, front-loaded sentence that states the primary action first and then lists specific aspects (AIO, structured content, APIs, metadata, AI-readable info). It contains no filler or redundant words.
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 the tool's simplicity (zero parameters, no output schema), the description adequately covers the scope by explaining what information will be provided. It could be more explicit about the response format, but for an informational endpoint it is complete enough.
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 tool has zero parameters, so the baseline is 4. The description appropriately adds no parameter details since none exist, and the empty schema already fully covers the parameter space.
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 specific verbs ('Answers', 'explains') and identifies a clear resource: AI discoverability. It distinguishes from sibling info tools by focusing on a distinct topic, though it doesn't explicitly name alternatives.
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?
The description implies when to use this tool (when information about AI discoverability is needed), but it provides no explicit when-not-to-use guidance or mentions of alternative tools. The usage is inferred rather than 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.
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.
