calculate_mortgage

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

No annotations provided, so the description carries full burden. It indicates this is a calculation tool with no destructive side effects. It specifies 'annuity' payment, adding context beyond the schema. However, it does not disclose the exact output format or any rounding behavior.

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 concise sentence that front-loads the verb 'Calculates'. It is efficient but could include more detail about the output or assumptions without becoming verbose.

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 calculation tool with three well-described parameters and no output schema, the description is fairly complete. It covers the inputs and what the tool does, but could explicitly state the output (monthly payment) and assumptions (e.g., fixed rate, monthly compounding).

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 baseline is 3. The description repeats the parameter names (principal, annual interest rate, loan term) but does not add new details beyond the schema's own descriptions. No additional clarification on units or format.

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 monthly mortgage payment using principal, interest rate, and term. It is distinct from sibling tools (get_branch_info, get_exchange_rate) which cover unrelated domains.

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 does not explicitly state when to use this tool versus alternatives, but the sibling tools are clearly different (branch info and exchange rates), so the usage context is implied. No exclusions or prerequisites are mentioned.

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