Calculate maximum home price you can afford

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

Adds non-obvious behavioral context beyond annotations: 'No network — pure local math' and identical math to zillow-mcp/redfin-mcp, plus the output breakdown. This helps the agent understand execution characteristics without contradicting the readOnly/idempotent hints.

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?

Every sentence earns its place: a precise headline, a compact input enumeration, a clear output summary, and implementation caveats. It is concise and well-structured with no 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?

For a 10-parameter calculator with no output schema and no parameter descriptions, the definition under-specifies units, defaults, and custom DTI overrides. The required fields are clear, but optional inputs remain ambiguous enough to affect correct use.

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 0%, so the description must compensate. It lists most inputs and clarifies monthly debts, but omits front_end_dti and back_end_dti, and does not specify units or default conventions for interest rate, property-tax rate, or insurance. This leaves ambiguity for correct invocation.

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 a specific operation: solving for the maximum affordable home price under the 28/36 DTI rule, with explicit outputs. It is clearly distinguishable from search/get/property tools, but it does not explicitly differentiate itself from the sibling homes_calculate_mortgage.

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 rule and outputs imply this is for affordability calculations, but there is no explicit when-to-use vs alternatives guidance. Mentioning 'Identical math to zillow-mcp and redfin-mcp' gives external context but does not compare it to internal siblings.

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