calculate_mortgage

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

No annotations are provided, and the description only reveals that it uses live rates from an external API. It does not disclose whether the tool is read-only, what errors might occur, network dependencies, or any limitations, leaving the agent without crucial safety or behavior context.

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 immediately states the action and key context. Every word earns its place with no redundancy.

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?

While the schema fully documents all 10 parameters, the description lacks any mention of return value format or potential limitations (e.g., unsupported states). The complexity of external API usage and optional parameters calls for more context, but the core purpose is adequately communicated for a straightforward calculator if the agent can infer the output.

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%, with detailed parameter descriptions in the schema itself. The tool description adds no parameter-specific semantics beyond saying 'live state-specific rates,' which is already captured in the state parameter description.

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 function with a specific verb ('Calculate') and resource ('monthly mortgage payment'), and adds context ('live state-specific rates using HomeSlice API'). This distinguishes it from the sibling get_mortgage_rates, which presumably only retrieves rates.

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 implies the tool is used for mortgage payment calculations but provides no explicit guidance on when to use it versus get_mortgage_rates. There are no exclusions, prerequisites, or alternative tool references.

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