Guidance on entity structuring for real estate investments — LLC formation, Series LLC availability, asset protection, and financing implications. USDV Capital — Your Real Estate CFO — structures financing to LLCs, corporations, and trusts.
| Name | Required | Description | Default |
|---|---|---|---|
| state | Yes | State | |
| annualRevenue | No | Annual rental revenue | |
| numProperties | No | Number of properties | |
| investmentStrategy | No | Investment strategy |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, and non-destructive behavior, so the description doesn't need to restate this. It adds useful context about the topics covered (LLC formation, asset protection, financing implications) and the types of entities handled (LLCs, corporations, trusts), which helps set expectations. No contradiction with annotations.
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 and front-loaded with the core purpose. The second sentence, while somewhat promotional, adds context about the types of entities and financing. It is concise overall with no significant redundancy.
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 an informational guidance tool with well-documented parameters and rich annotations, the description is adequately complete. It states the topic and scope. The only minor gap is that it does not explicitly describe the output format, but since it provides 'guidance,' the expected return is implied.
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 each parameter already has a description. The tool description does not add additional meaning or explain how the parameters influence the guidance beyond the schema, so baseline 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 clearly states the tool provides 'Guidance on entity structuring for real estate investments' with specific subtopics like LLC formation, Series LLC availability, and asset protection. It uses a specific verb ('Guidance on') and a specific resource, distinguishing it from sibling calculators and market 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 implies usage when entity structuring guidance is needed, but it does not explicitly state when to use this tool versus alternatives or mention any exclusions. There is no reference to sibling tools or conditions where a different tool would be more appropriate.
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 have clearly distinct purposes, especially the calculators and utilities. The markets-* group has five tools that all return market data, but each has a distinct focus (compare, nearby, screener, search, stats) with descriptions that clarify the differences. Overall, an agent can generally tell them apart, though the market tools could still cause minor confusion.
The naming convention is consistent across categories using lowercase with hyphens and a prefix (action-, calc-, deal-, eligibility-, markets-, util-). Within categories there is slight inconsistency, such as action-consultation (noun) vs action-prequalify (verb) vs action-send_report (verb_noun), but the overall pattern is predictable and readable.
With 23 tools, the server covers a broad range of real estate CFO services: property analysis, market intelligence, eligibility, and client actions. This is slightly on the heavy side but each tool serves a distinct purpose within the domain. It could be trimmed, but the count is not unreasonable given the scope.
The tool set covers the core lifecycle of a real estate deal: market research, property-level analysis, calculators for various strategies, eligibility checking, and client engagement actions. Minor gaps exist—such as no tool for tracking existing deals or a general mortgage payment calculator—but the main workflows are well supported. Completeness is strong for the stated purpose.
