calculate_mortgage_insurance

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

No annotations provided; description only states return format without disclosing behavioral traits such as side effects, permissions, or limits. Minimal transparency for a tool that likely reads data but could have side effects.

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?

Two sentences: first states purpose and return format, second points to related tools. No wasted words, perfectly concise for a simple calculator.

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 simplicity and full schema coverage, description adequately covers purpose, return format, and context for similar tools. No gaps for typical usage.

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% for all 3 parameters, so description adds no additional semantic value. Baseline 3 is appropriate as schema does the heavy lifting.

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 clearly states 'Calculate mortgage insurance cost' with specific verb and resource. It distinguishes from sibling tools like 'calculate_mortgage' by specifying insurance type and referencing related bundles.

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?

Description implies use for mortgage insurance calculation but lacks explicit when-to-use, when-not-to-use, or alternatives. Reference to list_bundles provides some context but no exclusion criteria.

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