ecl_computation__scenario_weighted_ecl

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

No annotations provided. Description does not disclose any behavioral traits beyond the weight constraint. Missing details on side effects, permissions, or return behavior.

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 is concise but lacks structure (e.g., no separate lines for purpose, parameters, constraints). Could benefit from bullet points but is not overly verbose.

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 provided. Description does not explain what the tool returns (e.g., a single ECL value or weighted sum). For a computation tool, this is a significant gap.

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?

Both parameters (scenario_ecls and weights) have no descriptions in schema. Description only mentions the weight constraint but not the expected format or structure. Scenario_ecls is completely unexplained.

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?

Description clearly indicates probability-weighted ECL across macro scenarios, distinguishing it from sibling tools like single-period or lifetime ECL. However, it does not explicitly state the action verb (e.g., 'calculates'), but the context implies computation.

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?

Only constraint given is that weights must sum to 1. No guidance on when to use this tool versus alternatives like ecl_single_period or lifetime_ecl, nor any context about prerequisites or scenario dependencies.

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