calculate_housing_loan_comparison

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

With no annotations, the description must provide behavioral context. It mentions the tool returns a structured result with 'offers_count, best_offer, comparison', but does not disclose whether the tool is read-only, requires authentication, or handles errors. The description is adequate but not fully transparent.

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 two sentences, front-loaded with the purpose, and includes a clear indication of the return structure and a cross-reference. No unnecessary words or 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 covers the main purpose and return structure, which is sufficient given the well-defined schema and the tool's straightforward nature. It lacks details on edge cases or error handling, but overall it provides enough context for an AI agent to use the tool correctly.

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 coverage is 100%, so the schema already documents parameters thoroughly. The description adds context by explaining that the 'offers' parameter expects multiple mortgage offers for comparison and that the tool computes a sorted result, adding meaning beyond the schema.

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 'Compare multiple mortgage offers sorted by total cost', which is a specific verb+resource combination. It distinguishes itself from siblings like 'calculate_mortgage' or 'calculate_loan_payment' by focusing on comparison of multiple offers.

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 clearly indicates this tool is for comparing multiple offers, implying when to use it. It also cross-references 'list_bundles' for related calculators. However, it does not explicitly state when not to use it or list alternatives for single-loan calculations.

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