camelot_bank_csv_normalizer

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

Annotations already cover idempotency and non-destructiveness. The description adds genuinely useful behavioral context beyond the schema: local browser processing, input format (pasted spreadsheet rows), and a guaranteed consistent five-column CSV output. This is meaningful additional transparency, though not exhaustive.

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 compact and front-loads the core purpose before the auxiliary local-processing note. The double period and the canonical URL are minor blemishes, but the text does not waste an agent's attention.

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 simple two-parameter tool with an output schema, the description plus annotations is largely complete: it explains the input, output shape, privacy-relevant local processing, and safety profile. It does not list the exact five columns, but the output schema can carry that detail.

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 description coverage is 100%, so the schema already documents rawTransactions and dateFormat. The description loosely reinforces the rawTransactions input but adds no extra meaning about dateFormat or parameter syntax beyond what the schema provides.

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 names a specific action and resource: pasting spreadsheet rows and normalizing them into a consistent five-column CSV. This clearly differentiates it from sibling tools like camelot_json_to_csv and the many finance calculators, none of which handle raw bank transaction normalization.

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 gives clear usage context: users copy transaction rows from a spreadsheet and paste them in, with processing happening locally in the browser. It does not explicitly compare against alternatives, but the narrow domain and unique output format make the intended use apparent.

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