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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds some useful context about escrow, PMI, extra payments, and PMI cancellation, but it does not describe the precise return shape or whether results include amortization schedules or only summary figures.

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-loads a concrete example before listing additional capabilities. The URL is somewhat promotional, but overall there is little wasted text and the main idea is easy to grasp.

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, the description should clarify what the tool returns beyond the single monthly-payment example. It mentions PMI cancellation and extra payments, but does not explain whether the output includes total interest, payoff timing, amortization details, or just summary payment figures.

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 every parameter is already documented in the schema. The description's example illustrates price, down payment, and rate, but it does not add meaning beyond the schema for parameters like HOA, tax, insurance, currency, or extra payment.

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 a concrete example and names the key capabilities: monthly payment, escrow, PMI, extra payments, and PMI cancellation. It is clear this is a mortgage payment calculator, but it does not explicitly distinguish itself from sibling mortgage tools such as canadian_mortgage_calculator, fha_loan_calculator, or interest_only_mortgage_calculator.

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?

There is no explicit guidance on when to use this tool versus alternatives, nor any when-not-to-use conditions. The feature list implies typical mortgage payment scenarios, but the large set of sibling mortgage calculators makes the lack of routing guidance a real gap.

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