mortgage_calculator

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

With no annotations, the description carries the disclosure burden. It provides defaults and units for inputs and states the output as 'monthly mortgage payment,' but it does not disclose the calculation formula, rounding behavior, or any input constraints (e.g., downPayment percentage range).

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 a single efficient sentence, front-loaded with the output and followed by compact parameter details. Every word contributes value with no repetition.

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 is sufficient for invoking the tool: it lists all required and optional inputs with defaultsable. However, the absence of an output schema means the exact return format (e.g., formatted number vs. detailed breakdown) is not specified, and invalid input handling is unaddressed.

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 names all four parameters with units and defaults: homePrice, downPayment (%) default 20, years default 30, annualRate (%) default 6.5. This fully clarifies the schema's bare parameter definitions.

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: 'Monthly mortgage payment.' This identifies the output resource and the domain. However, it does not explicitly differentiate from the sibling loan_calculator, which could serve a similar 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 purpose is implied by the name and description: use for mortgage payment calculations. There is no explicit guidance on when to choose this tool over sibling calculators like loan_calculator, and no exclusions are provided.

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