ecl_computation__lifetime_ecl

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

No annotations exist, so description carries full burden. It reveals a formula detail (sum over periods, t starts at 1) but omits side effects, safety profile, assumptions (e.g., constant EIR), or return value format.

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?

Single sentence, front-loaded with key computation detail. No redundant information, but could be expanded slightly without losing conciseness.

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?

No output schema; description does not explain what the tool returns. Lacks explanation of input parameters and their roles. Incomplete for a complex financial calculation with 4 inputs.

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 0%; parameters are not described. The description mentions 'marginal-PD-weighted' which aligns with 'marginal_pds' but provides no meaning for 'eir', 'eads', 'lgds'. Fails to compensate for missing schema descriptions.

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 states it computes Lifetime ECL as a sum of marginal-PD-weighted discounted losses per period, which is clear and specific. It distinguishes from sibling tools like 'ecl_single_period' via the 'Lifetime' qualifier, but does not explicitly differentiate from other ECL tools.

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. No prerequisites, exclusions, or context for selection among sibling ECL computation tools.

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