list_llc_dissolution_feesList the LLC dissolution filing fee for all 50 US states and DC, quoted exactly as each state publishes it, marking the states where the filing fee is not the whole cost. Use when someone compares costs across states or asks which states charge to close an LLC.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds meaningful behavioral context: fees are quoted exactly as published, and states where the fee is not the whole cost are marked. This goes beyond the annotations without contradicting them.
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 long, front-loaded with the action and scope, and includes usage guidance without any redundant wording. It is a model of conciseness.
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 read-only, zero-parameter list tool with no output schema, the description fully explains what is returned (fees for all states, exact quotes, cost warnings) and when to use it. Nothing essential is missing.
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 schema fully covers everything. Per the calibration, a zero-parameter tool gets a baseline of 4, and the description appropriately does not need to explain parameters.
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 the specific verb 'List' with a clear resource: 'LLC dissolution filing fee for all 50 US states and DC'. It also notes the exact quoting behavior and cost warning, distinguishing it from sibling tools that cover costs of not dissolving or requirements.
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 explicitly states when to use the tool: 'when someone compares costs across states or asks which states charge to close an LLC.' It does not mention exclusions, but the sibling tool names make the alternative contexts clear, so the guidance is sufficiently useful.
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 addresses a distinct user need: ongoing costs of abandoning an LLC, requirements for dissolving in a specific state, and cross-state fee comparison. There is no meaningful overlap between the tools, so an agent can reliably select the right one.
All tool names use snake_case and are descriptive, but two follow a verb_noun pattern (get_, list_) while the third is a noun phrase (cost_of_not_dissolving_llc). This minor inconsistency does not obscure meaning.
Three tools is a well-scoped count for a focused informational server. Each tool earns its place by covering a distinct aspect of LLC dissolution, fitting within the ideal 3-15 range.
The server covers the primary informational needs: cost of inaction, state-specific requirements, and fee comparisons. A minor gap is the lack of a dedicated tool for computing total dissolution cost from both filing and ancillary fees, but this is partially addressed within get_llc_dissolution_requirements.