add_flows

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

No annotations are provided, so the description carries the full burden. It discloses the upsert behavior, stating that each entry overwrites if a combination of fields exists. This is a key behavioral trait for a mutation 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?

Three concise sentences with no fluff. The first sentence states the core function, the second gives usage guidance, the third explains critical behavior. Front-loaded and efficient.

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?

Covers purpose, usage, and a key behavioral rule (overwrite condition). No output schema, but the description does not need to explain return values. Could mention error handling, but overall sufficient for a bulk import tool.

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 one parameter 'entries' with a detailed schema that includes descriptions for each sub-field. The description adds the context of a spreadsheet import but does not add new parameter meaning beyond what the schema provides. Schema coverage is high, so baseline 3 is appropriate.

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 verb 'Bulk-upsert' and the resource 'cash flow entries'. It is distinct from siblings like 'add_flow' (singular) and provides a concrete use case: importing a spreadsheet with rows and columns.

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?

Explicitly says 'Use when importing an income/expense spreadsheet...', giving clear context. Does not explicitly mention when not to use, but the sibling list includes 'add_flow' for single entries, implying the alternative.

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