Suggests which insurance coverages a business likely needs, ranked by importance.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | ||
| vertical | No | ||
| naics_code | No | ||
| serves_food | No | ||
| has_vehicles | No | ||
| does_delivery | No | ||
| employee_count | No | ||
| serves_alcohol | No | ||
| business_description | Yes | ||
| handles_customer_data | No | ||
| has_physical_location | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations, so the description carries full burden. It mentions ranking by importance but does not disclose how suggestions are determined, what inputs are used, what output format to expect, or any limitations. This is insufficient for a tool with no annotation support.
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 sentence that is front-loaded with the main purpose and includes a key behavioral detail (ranking). It is concise and easily readable, though it could benefit from a bit more detail without losing efficiency.
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 has 11 parameters, no output schema, and no annotations, this short description is incomplete. It lacks guidance on how to use the inputs, what the output looks like, and any behavioral caveats. More detail is needed for an agent to use it effectively.
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 0% and the description provides no information about any of the 11 parameters. It doesn't even hint that business_description and state are required or how they influence suggestions. The description adds no meaning 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 clearly states the tool's function: it suggests insurance coverages needed by a business, specifically 'ranked by importance.' This distinguishes it from siblings like classify_business (classification) and get_carrier_recommendations (carrier recommendations).
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 usage for obtaining coverage recommendations but does not explicitly state when to use it vs alternatives or any exclusions. No context about prerequisites or overlapping tool usage is given, so it's only implied.
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 has a distinct purpose: classification, coverage suggestions, explanations, carrier recommendations, and agent handoff. There is no overlap between tools; even the recommendation-focused tools operate on different layers (coverage vs. carrier).
All tool names follow a consistent verb_noun snake_case pattern (classify_business, connect_with_agent, explain_coverage, get_carrier_recommendations, suggest_coverages). The naming is predictable and clearly indicates the action and target.
With 5 tools, the server is well-scoped for its purpose of guiding small businesses through insurance discovery and connection. Each tool serves a necessary step in the workflow, and none feel redundant or excessive.
The tool set covers the full journey from business classification to coverage suggestions, educational explanations, carrier recommendations, and human agent handoff. No obvious missing capabilities for the stated purpose of the server.