calc_loan_amortization

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'COMPUTE. Level-payment loan schedule.' and does not explicitly state whether the operation is read-only, what output format is returned, or how optional parameters like extra_payment affect results. 'COMPUTE' implies a pure calculation but lacks explicit confirmation.

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 compact and front-loaded with the action, but the two fragments ('COMPUTE' and 'Level-payment loan schedule') are under-specified for a tool with six parameters. It is not verbose, but it lacks sufficient substance beyond a one-liner.

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?

With no output schema, no annotations, and a six-parameter input schema, the description should explain return shapes and optional parameter semantics. It only names the high-level output, leaving important context for correct invocation missing.

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%, and the description adds no meaning to principal, annual_rate, term_months, extra_payment, include_schedule, or currency. The agent must rely entirely on parameter names, which may be ambiguous for optional parameters.

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 computes a 'level-payment loan schedule', with 'COMPUTE' as the specific action and 'loan schedule' as the resource. This distinguishes it from sibling calculators like calc_npv or calc_irr.

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?

No guidance is provided about when to use this tool versus alternatives, when not to use it, or any prerequisites. The description does not mention fixed-rate loans, required inputs, or relationships to sim_* tools.

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