isw_complete_credit

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

With no annotations, the description carries the full burden. It discloses high risk and the confirm requirement but lacks details on failure behavior, error handling, or return values. Adequate but not comprehensive.

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 conveying purpose, inputs, and risk. Front-loaded and efficient; no wasted words.

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, nested objects (extra) unexplained, and no mention of expected response or side effects. For a high-risk financial operation, this is insufficient context.

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 low (25%). The description mentions inquiryRef and OTP but provides no additional semantic meaning. The extra and confirm parameters are not explained beyond schema defaults. More parameter context is needed.

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 action ('Complete bank credit'), required inputs (inquiryRef and OTP), and risk level. It distinguishes itself from sibling tools like isw_credit_inquiry by being the completion step.

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?

The description implies this is the final step after a credit inquiry by mentioning inquiryRef and OTP. It highlights the need for confirm=true and high risk, offering clear usage context. However, it does not explicitly state when to use vs alternatives.

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