nexus_rwa_calculator

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

No annotations provided; description carries full burden. Clearly states it computes and returns RWA and capital requirement with specific percentages. No mention of side effects or permissions, but as a stateless calculator, behavioral expectations are adequately set.

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?

Two sentences, 15 words, no fluff. Front-loaded with purpose and output. Every phrase adds value.

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 the nested input and no output schema, description provides useful context on what is returned (total RWA and capital requirement) and the regulatory framework (Basel III, 10.5%). Slightly lacking in output structure detail, but adequate for a calculator.

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 field descriptions. Description does not add extra meaning beyond the schema. Baseline score of 3 appropriate as description relies on schema for parameter details.

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 states it computes portfolio RWA using Basel III Standardized Approach and specifies output (total RWA and capital requirement). Distinct from sibling tools which cover analysis, market data, cases, and VaR.

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 explicit when-to-use or alternatives guidance. Implicitly clear for RWA tasks given sibling tool names, but lacks explicit instruction on when not to use or which sibling handles related computations.

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