normalize_camt053

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description is not burdened with those. It adds value by explaining the output (canonical observed records ready to reconcile) and input flexibility (list or dict with specific keys), which goes beyond annotations.

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?

The description is two sentences long, each serving a distinct purpose: first sentence states the core function and output, second sentence details input flexibility. No redundant words, and key information is 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?

Given the tool's complexity (flexible input, conversion to canonical records) and the presence of an output schema and comprehensive annotations, the description covers the essential aspects. It could be slightly improved by mentioning expected input format constraints or error handling, but is largely complete.

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?

The schema description for the only parameter 'document' is generic, but the tool's description adds crucial details: it accepts a list of entries or a dict wrapping them under 'entries', 'transactions', or 'statements'. This significantly enriches the meaning beyond the schema.

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 tool converts parsed camt.053 statement entries into canonical observed records ready for reconciliation. It specifies the resource (camt.053 entries) and the action (convert), and the name itself distinguishes it from sibling normalize_pain001 (different standard).

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 does not explicitly state when to use this tool versus alternatives like normalize_pain001 or reconcile. It implies usage after parsing camt.053 and before reconciliation, but provides no guidance on when not to use it or prerequisites.

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