list_statesEvery US state with its average effective property tax rate, median home value and estimated annual tax. Sortable, so it answers 'which states have the highest property taxes' directly. Call this to discover valid state names for the other tools.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many states to return. | |
| order | No | Sort direction. | asc |
| sortBy | No | Ordering of the returned list. | name |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds beyond this by explaining the sortability feature (which directly answers 'which states have the highest property taxes') and confirming the complete coverage of all 50 states, which is useful behavioral context.
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 three sentences, front-loaded with the core purpose, then a practical use case, then a cross-tool hint. Every sentence earns its place with no redundancy or filler.
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?
Despite having no output schema, the description lists the returned data fields (tax rate, median home value, annual tax). Combined with the 100% parameter schema coverage and the annotations providing the safety profile, the description provides enough context for the agent to select and invoke the tool correctly.
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 description coverage is 100%, so the parameters (limit, order, sortBy) are already well documented. The description adds little beyond noting sortability, which indirectly relates to sortBy/order but does not materially enhance parameter understanding. Baseline of 3 is appropriate.
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 explicitly states the tool lists every US state with average effective property tax rate, median home value, and estimated annual tax. It also distinguishes itself from the sibling calculator tools by positioning this as a data listing tool and mentioning that it provides valid state names for other tools.
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 gives clear context: it is the tool to call for discovering valid state names for other tools, and it directly answers which states have the highest property taxes. It does not explicitly list when-not-to-use scenarios or alternative tools, but the sibling tools are all calculators, implying this is the dedicated listing tool.
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 calculation or information need: affordability, amortization, full mortgage payment, PMI, property tax, refinancing, rent vs buy, loan comparison, closing costs, state rules, and state list. Even overlapping tools like calculate_mortgage and calculate_pmi are clearly separated by depth and purpose.
All tool names follow a consistent verb_noun snake_case pattern, using verbs like calculate, compare, estimate, get, and list. The pattern is uniform and predictable across the entire set.
With 11 tools, the server is well-scoped for a US mortgage calculator domain. Each tool covers a meaningful aspect of mortgage analysis without redundancy or bloat.
The tool surface covers the full lifecycle of mortgage decision-making: affordability, payment estimation, amortization, PMI, property tax, refinancing, rent vs buy, loan comparison, closing costs, and state-specific rules. No significant gaps are apparent for the stated purpose.