isw_agency_cashout_xml

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

No annotations provided; description mentions it's 'high-risk financial operation' but lacks details on side effects, error behaviors, or success conditions expected for such a sensitive tool.

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, no unnecessary words, front-loaded with the core action.

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?

For a high-risk financial operation with no annotations, output schema, or parameter details on XML content, the description is insufficient for an agent to safely invoke it without additional 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 50% (only 'confirm' has description). Description reinforces 'confirm: true' but adds no meaning to the 'xml' parameter, which has no schema description.

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 'Submit raw Agency Banking cashout XML' with specific verb and resource, distinguishing it from siblings like 'isw_agency_banking_cashout' which likely uses a different format.

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 hints at caution ('high-risk', 'requires confirm') but does not specify when to use this tool over alternatives like 'isw_agency_banking_cashout' or 'isw_agency_requery_xml'.

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