debt_restructuring__npv_of_terms

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

No annotations are provided, and the description does not disclose assumptions (e.g., payment frequency, compounding method) or side effects. It only states the formula without behavioral 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?

A single sentence that efficiently conveys the tool's purpose. No wasted words; front-loaded with the domain tag and clear computation description.

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 no output schema and zero parameter documentation in the schema, the description lacks details on return values, assumptions, and edge cases. The tool might benefit from clarifying whether payments are annual, what discount rate format is expected, etc.

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%. The description adds minimal parameter context by mentioning 'interest-only payments' and 'bullet principal', but does not explain each parameter's role, units, or constraints.

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 specifies the exact computation: present value of interest-only payments and bullet principal at a discount rate. The tool name and context (debt restructuring) clearly distinguish it from siblings like haircut_pct and waterfall.

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 on when to use this tool versus alternatives. It does not mention scenarios where NPV of terms is appropriate or contrast it with other debt restructuring tools.

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