USDV Capital — Your Real Estate CFO

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate non-read-only, non-idempotent, open-world behavior. The description adds context that the advisor reviews deal details before the call, providing insight into what happens upon invocation. No contradictions 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?

Three sentences, about 40 words, front-loaded with the main purpose. Every sentence earns its place: purpose, logistics, and advisor preparation. No 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 a simple scheduling tool, the description fully covers the workflow: scheduling, duration, method, and advisor preparation. With schema handling parameter details and no output schema, this is sufficient for an agent to invoke 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 covers 100% of parameters with descriptive text, so baseline is 3. The description reinforces the dealDetails purpose but does not add new parameter semantics beyond what the schema provides.

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?

Description states 'Schedule a free consultation with a USDV Capital Capital Advisor' – a specific verb and resource that clearly distinguishes it from sibling action tools like action-prequalify. It also provides logistics (15-30 minutes, phone/video) that further define the tool's purpose.

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 for when to use: free consultation, no obligation, no credit check, and advisor preparation. However, it does not explicitly mention alternatives or when not to use, so it stops short of full when/when-not guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds useful behavioral context beyond annotations: no credit score impact, advisor follow-up within 24 hours, and a guaranteed response time. It does not fully disclose downstream effects like lead creation or data sharing, but the openWorldHint and non-readOnly annotations are supplemented by these customer-facing details.

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 starts with the purpose, which is good, but it includes redundant information: 'follows up within 24 hours' is repeated by 'guarantees response within 1 business day'. The marketing tagline 'Your Real Estate CFO' adds no functional value and could be trimmed.

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 12 parameters and no output schema, the description covers the high-level purpose and response expectations but omits details about return values, failure modes, or prerequisite user information. The input schema compensates for parameter detail, but the description does not fully round out the invocation context.

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 100% with descriptive parameter details, so the description does not need to explain each field. It provides no additional parameter-specific semantics beyond the overall context of a pre-qualification request.

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 submits a pre-qualification request to USDV Capital for a capital strategy assessment. It uses a specific verb+resource and distinguishes itself from sibling tools like action-consultation and eligibility-check by focusing on the pre-qualification action.

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 this tool is used when a user wants to submit a pre-qualification request, but it does not explicitly state when to use it versus alternatives like eligibility-check or action-consultation. There are no clear exclusion criteria or alternative tool references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description reveals the primary side effect (sending an email) and adds context beyond annotations (PDF format, free, no obligation, designed for sharing). Annotations declare readOnlyHint=false, so the agent already knows this is a write action; the description supplements with relevant behavioral details.

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, front-loaded with the main action, and contains no redundant information. Every sentence adds value (purpose and usage context).

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 5 parameters, nested object, and no output schema, the description is brief but supported by rich schema descriptions. It explains when to use the tool and the main action, though it does not detail return values. However, the schema and annotations cover most of the needed context.

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 schema fully documents parameters. The description does not add any parameter-specific meaning beyond what schema already provides, but the baseline of 3 is appropriate due to high coverage.

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 specific verb 'Send' and the resource 'a professionally formatted Capital Advisory Report (PDF) to an investor's email'. It distinguishes from sibling calculator tools by focusing on the action of sending a report rather than computing data.

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?

Explicitly states 'Use after running any calculator tool', which is a clear precondition for usage. It does not mention when not to use or alternatives, but the context is sufficient for tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this as read-only and non-destructive. The description adds behavioral context by outlining the modeled phases (buy, rehab, rent, refinance, repeat) and key outputs (cash invested, cash recovered, infinite return). It also indicates that both acquisition financing and DSCR refinance are considered, which goes beyond the annotation information.

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 main purpose is front-loaded in a concise first sentence. The second sentence adds a marketing tagline ('USDV Capital — Your Real Estate CFO') but also mentions significant behavior (structuring both acquisition and DSCR refinance). It is not purely wasted, though it could be tighter. Overall, appropriately sized for the complexity.

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?

The description explains the high-level analysis but omits important behavior: the sendReportTo parameter can email a Capital Advisory Report, and there are detailed instructions about only using real emails. This is not mentioned in the description. Since there is no output schema, the description should clarify what the tool returns, but it only hints at outputs (infinite return). The tool has 13 parameters and the description gives a good overview but not full coverage of its behavior.

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 all 13 parameters already have descriptions. The tool description itself does not add any parameter-specific meaning beyond what is in the schema, which is sufficient. It mentions 'cash invested, cash recovered' but these are outputs, not parameters, so no additional semantic value is provided.

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 purpose: 'Analyze a BRRRR (Buy, Rehab, Rent, Refinance, Repeat) strategy' and details what the analysis covers ('all 5 phases including cash invested, cash recovered, and whether infinite return is achieved'). This specific verb+resource combination distinguishes it from sibling calculators like calc-flip_roi, calc-rental_cashflow, and calc-dscr.

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 provides clear context: it is for BRRRR strategy analysis specifically. However, it does not explicitly state when not to use it or mention sibling alternatives. The context is unambiguous enough for an agent to select it for BRRRR-related queries, though exclusions are not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds useful output details (itemized breakdown, timeline, contingency) and the financing context (USDV Capital), which hints at possible financing-related outputs. However, the financing sentence is promotional and not a clear behavioral disclosure.

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 first sentence is concise and informative. The second sentence is a marketing tagline for USDV Capital, which does not help an agent select or invoke the tool correctly, reducing the overall efficiency of the description.

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?

The tool has 7 parameters and no output schema, so the description must clarify return values. It lists key outputs (itemized costs, timeline, contingency) but the financing sentence adds ambiguity about whether financing offers are included. The description is adequate but not fully complete for an agent to anticipate all responses.

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 schema already documents all parameters. The description mentions 'location, scope, and property type' but adds no additional detail beyond what the schema provides, thus not elevating the baseline score.

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 estimates construction and renovation costs, with a specific verb ('Estimate') and resource ('construction and renovation costs'). It also lists key inputs (location, scope, property type) and outputs (itemized cost breakdown, timeline estimate, contingency recommendation), distinguishing it from sibling calculators like calc-brrrr or calc-flip_roi.

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 by stating the tool's function, but it does not explicitly mention when to use this tool versus alternatives or provide exclusions. No sibling tools are referenced, so an agent must infer when this is the right calculator based on the construction/renovation focus.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that it provides a 'full CFO-level assessment' and mentions a close guarantee, but these are more marketing statements than behavioral disclosures. It does not describe output format or side effects, so with annotations covering safety, a 3 is appropriate.

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 first two sentences are efficient and front-loaded with the core purpose and use case. However, the third sentence about USDV Capital's marketing promise is promotional and irrelevant for tool selection, adding noise. The description could be more concise.

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 tool with 11 parameters and no output schema, the description should clarify what the 'CFO-level assessment' contains and whether the tool sends email reports. It does not, leaving the agent to infer from the schema. The description is adequate but lacks key behavioral details.

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 schema covers 100% of parameters with descriptions, setting a baseline of 3. The description does not elaborate on parameter meanings, though it implies property types relevant for propertyType. It adds little beyond the schema, so the baseline holds.

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 calculates DSCR for rental properties and Airbnb short-term rentals, with a specific verb and resource. It distinguishes itself from sibling calculators like calc-rental_cashflow or calc-str_revenue by focusing on the DSCR metric, making the purpose unambiguous.

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 explains that DSCR is used for rental loans qualifying on property cash flow rather than personal income, and explicitly mentions applicability to long-term rentals, Airbnb/VRBO, and BRRRR refinance. This provides clear context, though it does not name alternate tools or exclusions, resulting in a slight deduction.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already signal readOnly and idempotent behavior, and the description adds context by listing what the calculation covers (capital gains, depreciation recapture, taxes deferred, deadlines). It also mentions financing structuring, though it doesn't disclose assumptions or limitations.

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 first sentence is concise and informative, but the second sentence includes a promotional pitch with an ambiguous phrase ('28 days or $1,000 close') that doesn't help an agent select or invoke the tool. This unnecessary content prevents a higher score.

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 7-parameter calculator with no output schema, the description provides enough context about expected results (capital gains, recapture, deferred taxes, deadlines). It lacks return format details and caveats, and the financing text adds noise, so it is not fully complete.

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% and all parameter descriptions are self-explanatory. The tool description does not add parameter-level syntax or format details, so the 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's verb ('Analyze', 'Calculates') and specific resource ('1031 exchange scenario for tax deferral'). It lists concrete outputs (capital gains, depreciation recapture, estimated taxes deferred, key deadlines), which distinguishes it from other real estate calc siblings.

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 clearly implies use for 1031 exchange scenarios and tax deferral analysis, which differentiates it from sibling calculators like calc-flip_roi or calc-rental_cashflow. However, it does not explicitly state when not to use it or name alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint, lowering the bar. The description adds useful context about included cost components and capital strategy assessment, but it also includes a promotional sentence about USDV Capital financing that doesn't describe tool behavior and omits mention of the sendReportTo (email report) feature. This is a moderate addition beyond annotations, not a full disclosure.

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 first two sentences are efficient and front-loaded, but the final sentence about USDV Capital's financing terms is irrelevant to tool usage and does not earn its place. This extraneous marketing content prevents a higher conciseness score.

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?

With no output schema, the description should clarify what the tool returns (e.g., ROI figure, breakdown, report). It lists cost categories but does not state the output format, and it fails to mention the sendReportTo capability entirely. While the schema covers the email parameter, the description leaves ambiguity about the tool's overall behavior for an agent.

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 input schema provides 100% parameter descriptions, so the baseline is 3. The tool description does not add any parameter-specific details beyond what the schema already covers; it just references cost categories that map to existing properties without elaborating formats or constraints.

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 opens with a specific verb and resource: 'Calculate projected ROI for a fix-and-flip or house flip project.' It enumerates cost categories and profit analysis, and explicitly notes BRRRR acquisition phase applicability, which distinguishes it from sibling calculators like calc-brrrr or calc-rental_cashflow.

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 for flip projects and also useful for BRRRR acquisition phase analysis. However, it does not explicitly name alternative tools or state when not to use it, so it misses the full 'when/alternatives' guidance that would merit a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds scope and output metrics but omits the optional email-report behavior tied to sendReportTo, which is only disclosed in the parameter schema, leaving a transparency gap.

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 compact with two functional sentences and a marketing tagline. The first sentence front-loads the core purpose, and the second lists outputs and use cases. The tagline is non-essential but not misleading, so it earns a strong score.

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?

With 13 parameters and no output schema, the description adequately summarizes output metrics and use cases. However, it misses the optional email-report side effect and doesn't describe the return format beyond the metric list, leaving a minor completeness gap given the tool's complexity.

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 input schema has 100% description coverage for all 13 parameters, including extensive guidance on sendReportTo. The description adds no parameter-level detail beyond the schema, so it meets the baseline without enhancing parameter semantics.

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 states a specific verb ('Analyze') and resource ('cash flow for a rental property'), listing concrete outputs (NOI, cap rate, cash-on-cash return, DSCR) and property types (long-term rentals, Airbnb, buy-and-hold). This clearly distinguishes it from sibling calculators like calc-brrrr, calc-dscr, and calc-str_revenue.

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 says it works for long-term rentals, Airbnb, and buy-and-hold analysis, giving clear context for when to use it. However, it does not name alternatives or provide when-not-to-use exclusions, though sibling tool names imply different analysis types.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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 agent knows it is a safe calculation. However, the description omits the side effect of sending a report when sendReportTo is provided, which is a meaningful behavioral detail not covered by annotations. The marketing sentence about DSCR loans adds noise, not transparency.

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 has three sentences: the first is functional, the second lists outputs, and the third is promotional ('USDV Capital — Your Real Estate CFO — structures STR financing...'). The third sentence does not earn its place for tool selection or use, making the description less concise than it could be. Front-loading is okay, but the marketing fluff reduces 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?

The description covers the purpose and main output categories, but it misses the capability to send a Capital Advisory Report via the sendReportTo parameter, which is a significant feature. It also does not specify that location, state, and bedrooms are required, nor mention optional parameters like purchasePrice. Given no output schema, the description should provide a more complete picture of behavior and requirements.

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 are already well-documented. The description adds minimal value by mentioning location, bedrooms, and property type in the first sentence, but it does not elaborate on parameters like purchasePrice, nightlyRateOverride, or sendReportTo beyond what the schema already provides. 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 estimates short-term rental (Airbnb/VRBO) revenue potential based on location, bedrooms, and property type, and lists specific outputs (occupancy projections, ADR estimates, seasonal breakdown, comparison to long-term rental income). This distinguishes it from sibling calculators focused on other metrics.

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 estimating STR revenue (e.g., 'Estimate short-term rental revenue potential'), but it does not explicitly state when to use this tool versus other calculators like calc-rental_cashflow or calc-dscr, nor does it mention alternatives or exclusions. Usage is implied rather than explicitly guided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already communicate read-only, idempotent, and non-destructive behavior. The description adds valuable context about the output (a deal score from 1-100) and the components included (market intelligence, financial projections, etc.), which goes beyond what annotations provide. No contradictions 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 only two sentences, front-loaded with the core action and scope. Every sentence adds value, explaining what the analysis combines and which strategies it supports. The branding phrase 'Your Real Estate CFO' is minor and does not detract from clarity.

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 complexity (14 parameters, no output schema), the description provides a strong high-level overview, including the main output (deal score) and supported strategies. However, it does not detail the return structure or how parameters affect the analysis, which would be useful but is not strictly required for selection.

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?

All 14 parameters have schema descriptions, so the baseline is 3. The tool description does not add parameter-specific meaning, but it does provide high-level context around how the parameters relate to the analysis types. With 100% schema coverage, the description need not compensate.

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 'Run a comprehensive deal analysis' with a specific verb and resource, and distinguishes it from sibling tools by positioning it as the 'signature assessment' that combines multiple analyses into a single CFO-level evaluation. It also enumerates supported investment strategies, giving concrete scope.

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 context by listing supported strategies and the comprehensive nature of the analysis, but it does not explicitly contrast with alternatives like the calc-* or markets-* sibling tools, nor does it state when not to use this tool. The guidance is implicit rather than explicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint and idempotentHint, and the description adds behavioral context by stating the return value (matching capital solutions with estimated terms) and geographic/amount coverage. This complements the annotations without contradiction.

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 with the core statement front-loaded. The second sentence, while containing a marketing tagline, provides useful scope information about state coverage and loan amounts. No redundant or overly verbose content.

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?

With 6 parameters, 4 required, and no output schema, the description explains the return type and covers scenario types plus state/amount range. It does not detail parameter formats, but those are in the schema, making it sufficiently complete for a read-only eligibility tool.

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 descriptions cover 100% of parameters, providing baseline 3. The description adds value by enumerating investment scenarios (fix and flip, BRRRR, etc.) that map to loanPurpose/propertyType concepts, and by mentioning the $150K-$10M range, which clarifies loanAmount limits.

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: checking financing availability through a specific network for various real estate investment scenarios. It lists concrete scenario types (fix and flip, DSCR rental, etc.) and specifies the return of matching capital solutions with terms, distinguishing it from siblings focused on calculations or prequalification.

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 use for eligibility checks but provides no explicit guidance on when to use this tool versus sibling tools like action-prequalify or eligibility-products. It does not state exclusions or alternatives, leaving the agent to infer the appropriate context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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 clear. The description adds useful context about the breadth of products covered (flipping, Airbnb, BRRRR, multifamily), which goes beyond the annotations. No contradictions.

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?

Three sentences, with the first front-loading the primary purpose and the second listing coverage. The final marketing sentence ('USDV Capital — Your Real Estate CFO...') is promotional filler that doesn't help an agent select or invoke the tool, keeping it from a 5.

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?

The tool is simple (one optional param, no output schema), and annotations cover safety. The description adequately explains what products are covered and hints at the return ('detailed information'). It doesn't detail output format, but given low complexity and strong annotations, it is sufficiently complete.

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% (the single parameter product_type has a clear description). The tool description does not elaborate on parameter usage, but the schema already documents it. Baseline 3 applies because the description adds no additional parameter meaning.

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 'Get detailed information about capital solutions' with a specific resource (capital solutions) and enumerates concrete product types (Fix & Flip, DSCR, bridge, construction). This distinguishes it from siblings like eligibility-check and calc-* calculators, which focus on eligibility and calculations.

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?

No explicit when-to-use or alternative guidance is provided. The description implies usage through its product list, but it doesn't explicitly say when to choose this over eligibility-check or other related tools. Context is present but not directly stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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 covered. The description adds useful context about the 2-5 market limit and side-by-side comparison, but it does not disclose other behavioral traits such as output format, data sources, or any limitations beyond the count. It provides some extra value beyond annotations but not rich detail, warranting a 3.

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 concise and front-loaded with the core purpose in the first sentence. The second sentence provides useful usage context. However, the final tagline 'USDV Capital — Your Real Estate CFO.' is promotional and does not add functional value for an AI agent, preventing a perfect score.

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 relatively simple tool with one well-documented parameter and clear annotations, the description covers the essential context: what it compares (investment metrics), how many markets (2-5), and the analytical level (CFO-level). It does not explain the return structure, but the lack of an output schema is mitigated by the tool's straightforward comparison nature. This is nearly complete for the tool's complexity.

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 input schema fully documents the 'locations' parameter with type, min/max items, and nested properties (name, state), giving 100% schema description coverage. The description reinforces the 2-5 market scope but does not add new parameter-level information. Since the schema already explains the parameters thoroughly, a baseline score 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 clearly states the tool's function: 'Compare real estate investment metrics across 2-5 US markets side-by-side with CFO-level analysis.' The verb 'Compare' plus the explicit resource (real estate investment metrics) and scope (US markets) makes it distinct from sibling tools like markets-stats or calc-* tools. It directly communicates the tool's purpose without ambiguity.

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 provides a clear use case: 'Ideal for investors deciding where to deploy capital.' This tells the agent when to use this tool. However, it does not explicitly state when not to use it or name alternative tools for different scenarios, so it falls short of a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavioral context by stating it 'Returns markets sorted by distance with investment metrics,' which informs the agent about the output format and ordering. There is no contradiction with annotations, and no additional behavioral traits (e.g., rate limits) are disclosed, but the output behavior is a meaningful addition.

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 concise, with the main functionality and output behavior in two short sentences. However, it includes a third sentence, 'USDV Capital — Your Real Estate CFO,' which is a brand tagline that adds no value for an AI agent and could be considered noise. Overall, the structure is front-loaded and efficient, but the tagline slightly reduces the 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?

Given the complexity (5 parameters, no output schema) and the presence of rich annotations, the description is reasonably complete. It covers the core purpose and output behavior. However, it does not mention the ability to filter by 'type' (state, county, city, etc.), which is a key parameter in the schema, nor does it describe the return structure in more detail. Still, the schema and annotations fill most gaps, making this description adequate.

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%, with all five parameters having explicit descriptions (e.g., 'Latitude', 'Longitude', 'Search radius in miles (default 25)'). The description does not add new meaning to the parameters; it merely mentions 'within a radius,' which aligns with the existing schema. Since the schema carries the parameter documentation, the description is not required to compensate, but it also does not enhance the parameter semantics.

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: 'Find nearby real estate markets within a radius using PostGIS proximity search.' It specifies a distinct verb ('Find') and resource ('nearby real estate markets') and mentions the output ('Returns markets sorted by distance with investment metrics'). This distinguishes it from sibling tools like markets-search or markets-screener by focusing on proximity/radius search rather than general search or screening.

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 provides clear context for when to use the tool: when you need to find markets near a geographic location within a radius. It does not explicitly state when not to use it or mention alternatives, but the first sentence implies the specific use case. Sibling tool names (e.g., markets-compare, markets-stats) offer further context, but the description itself gives no explicit exclusions or alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds context about the data being 'pre-computed for 18,800+ cities' and the score components, but does not disclose return format, pagination, or other behavioral traits. This is consistent with the calibration example for get_calls.

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 concise and front-loaded with the core purpose, followed by use cases. However, it includes a marketing tagline 'USDV Capital — Your Real Estate CFO' which is unnecessary noise and slightly detracts from 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 simple read-only screener with 3 optional parameters and no output schema, the description adequately covers what it does and when to use it. It does not explicitly describe the return format, but the purpose is clear enough. The annotations and schema cover most other details.

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%, and all parameters (limit, state, min_score) have descriptions. The description mentions the 'investment score (0-100)' which relates to min_score, but adds no additional meaning beyond the schema definitions. 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's function: 'Screen US cities by composite investment score (0-100)' with specific criteria. It distinguishes from siblings like markets-search or markets-compare by focusing on screening by investment score, though it does not explicitly name or contrast with those siblings.

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 provides clear usage context: 'Ideal for finding markets for fix and flip, Airbnb short-term rental, BRRRR, ground up construction, or buy-and-hold strategies.' It tells the agent when to use this tool but does not mention alternatives or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description is consistent with these. It adds useful context beyond annotations by specifying geographic coverage (all 50 states, DC, PR) and the type of data returned (home values, rents, cap rates, population), which helps the agent understand behavior without contradicting the 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 front-loaded with the key information in the first sentence, naming the database, scope, and return content. The second sentence is a promotional tagline ('USDV Capital — Your Real Estate CFO') that does little to help an agent invoke the tool, but it is short and does not significantly bloat the description.

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 there is no output schema, the description adequately explains what the tool returns by listing examples of CFO-level market data. It also covers the searchable geographic scope, which combined with the well-documented schema gives an agent enough context to use the tool correctly in most situations.

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 input schema already documents all four parameters (query, type, limit, state) at 100% coverage, so the description does not need to repeat them. The description does not add extra semantic detail beyond the schema, but the schema itself is sufficient, making the baseline score of 3 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 identifies the tool as a search over a specified real estate market intelligence database, covering all US states plus DC and Puerto Rico. It states the resource and the action, but does not explicitly contrast with sibling tools like markets-screener or markets-compare, so it loses the top score.

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?

Usage is implied by the verb 'Search' and the database context, suggesting it is appropriate for finding market data by location. However, there is no explicit guidance on when to prefer this tool over sibling tools such as markets-screener or markets-stats, nor any exclusion criteria.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark it as read-only and idempotent. The description adds useful context about data sources (Census ACS 2023, Zillow Feb 2026) and the breadth of data, but does not disclose output format or any potential limitations. This goes beyond annotations but not significantly.

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 short and front-loaded with the primary purpose. The first sentence is dense with useful information. The branding at the end (USDV Capital — Your Real Estate CFO) is non-essential but does not significantly hurt 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 market statistics tool with two simple parameters, the description covers what data will be returned, data sources, and location scope. It lacks mention of output format, but the absence of an output schema makes this less critical. The level of detail is adequate for an agent to understand the tool's function.

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 100% for the two parameters, and descriptions exist for both. The tool description does not add extra meaning beyond the schema, so it meets the baseline but does not elevate it.

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 gets detailed real estate market statistics for a specific location, listing specific data categories. This distinguishes it from sibling tools like markets-compare (comparison) and markets-screener (screening) by emphasizing location-specific stats.

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?

No guidance is provided on when to use this tool versus alternatives like markets-search or markets-compare. The description does not mention exclusions or alternatives, so the agent receives no proactive selection help.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

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.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered. The description adds the behavioral detail that it includes 'flood zone assessment', which is useful beyond the schema, but it does not describe output format or any other operational traits.

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 first sentence is concise and valuable, but the second sentence is marketing fluff ('USDV Capital — Your Real Estate CFO...') that does not earn its place for an AI agent. The description would be stronger if it ended after the first sentence.

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 the marketing filler, the description is complete enough for a simple read-only estimation tool with full schema coverage and safety annotations. It clearly states what the tool does and a key feature (flood zone), and the absence of an output schema is mitigated by the simplicity of the expected result.

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%, with each parameter having a basic description. The tool description adds no additional meaning to the parameters, making the baseline score of 3 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 opens with a specific verb and resource: 'Estimate property insurance costs', clearly distinguishing it from sibling tools like util-property_tax and util-rent_estimate. The mention of 'flood zone assessment' adds a unique feature that further clarifies its scope.

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 through its purpose statement but provides no explicit guidance on when to use it versus alternatives. The second sentence about USDV Capital is more about the service context and does not help an agent decide between this and other estimation tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only and non-destructive, so the description's main contribution is listing the analytical outputs (demographics, income, etc.). This adds useful behavioral context beyond what annotations provide.

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 short and begins with the purpose, but includes an unnecessary brand tagline ('USDV Capital — Your Real Estate CFO') that adds no functional value. This prevents it from being optimally concise.

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 simple 2-parameter tool with no output schema, the description sufficiently explains what the tool does and what data it returns. It could be improved by mentioning the output format or clarifying location input, but it is adequately complete.

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 100% with simple descriptions for both parameters (location, state). The description does not add any additional parameter-level meaning beyond what the schema already provides, so it stays at the baseline of 3.

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 a detailed neighborhood or city analysis for investment due diligence, listing specific data points: demographics, income, employment, vacancy, housing stock, and investment grade. This specificity distinguishes it from sibling tools like markets-compare or markets-stats.

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 phrase 'for investment due diligence' provides a clear context for when to use this tool. However, it does not explicitly mention alternatives or exclusion criteria, which would elevate it to a 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds no further behavioral context such as data source, geographic coverage limitations, or response format. The claim 'for any county or city' is an overstatement without caveats, and the marketing tagline adds no behavioral insight.

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 first two sentences are front-loaded and efficient, but the third sentence 'USDV Capital — Your Real Estate CFO.' is pure marketing and does not earn its place for an AI agent. It is not verbose, but every sentence should serve tool selection and invocation; this one doesn't.

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 simple lookup tool with 3 parameters and no output schema, the description indicates what the tool returns ('rates and estimated annual taxes') and its use case. It lacks explicit mention of output units, tax year, or data freshness, but for the agent's selection purpose it is reasonably complete.

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 baseline is 3. The description reinforces that 'county or city' maps to the county parameter and that propertyValue is used for estimates, but it does not add new semantic meaning beyond the schema's existing descriptions.

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 opens with a specific verb and resource: 'Look up property tax rates and estimated annual taxes for any county or city.' This clearly distinguishes it from sibling tools like util-rent_estimate or util-insurance by focusing on property taxes. It is not a tautology or vague statement.

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?

It provides clear usage context: 'Essential for calculating holding costs in rental and flip analysis.' This tells the agent when to select this tool over others. It does not explicitly list exclusions or alternative tool names, but the context is sufficiently clear for a utility tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the tool read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds useful context about data sources (Zillow, Census, STR comparison, vacancy rates), but does not disclose the return format or any behavioral details such as potential complexity or limitations. This is a moderate gap given there is no output schema.

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 short and front-loaded with the primary function. The second sentence adds relevant data source context but ends with a marketing slogan ('USDV Capital — Your Real Estate CFO') that does not serve a functional purpose. Slightly less concise than ideal due to this non-essential addition, but still efficient overall.

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 tool with no output schema, the description provides a good sense of the tool's scope and inputs, but it does not clarify what the result looks like (e.g., a single number, a range, a report). It also omits any limitations (e.g., geographic coverage, data freshness). Given the simplicity of the tool and the presence of annotations, the description is adequate but not fully complete.

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 input schema provides descriptions for all three parameters (location, state, bedrooms), achieving 100% coverage. The description only restates that these inputs are used for the estimate, adding no additional semantics about formats, constraints, or examples. Baseline 3 is appropriate because the schema carries the burden.

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 a specific action ('Estimate fair market rent') and identifies the key inputs ('location and bedroom count'), distinguishing this tool from sibling calculators like cashflow or STR revenue. The title 'Get Rent Estimate' reinforces the purpose, making it immediately clear what the tool does.

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 context (for estimating rent based on location/bedrooms) but does not explicitly state when to use this tool versus alternatives like calc-rental_cashflow or markets-compare. There is no mention of exclusions, prerequisites, or alternate tools, so guidance is limited to implied context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.