parse_camt053

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

Discloses return format (ParsedCamt053 on success, error on failure) and intended purpose. No annotations exist, so description adequately covers behavioral traits for a read-only parsing 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?

Six sentences with no fluff. First sentence states action, second provides context, third explains return. Efficiently structured and front-loaded.

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?

Simple tool with one parameter and output schema present. Description explains business context (accounts statement, bank reconciliation) and return value. Complete for given complexity.

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?

Only parameter 'xml' is fully described in schema (100% coverage). Description adds no extra meaning beyond 'The camt.053 XML message as a string.' Baseline score of 3 applies.

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?

Specifically states 'Parse a camt.053.001.08 Bank-to-Customer Cash Management Statement', identifies the exact message type, and distinguishes from sibling tools (e.g., parse_pacs008) by focusing on a unique resource.

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?

Clearly describes when to use: for bank reconciliation with camt.053 statements. Does not explicitly state when not to use or list alternatives, but sibling context implies other parse tools for different messages.

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