cash_register_movements_create

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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive creation operation. The description adds useful business behavior: direction is auto-set for deposit/withdrawal, required for other, and movementDate is constrained by the cash account opening date.

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 tight sentences, front-loaded with the main action and followed by the two key rules an agent must apply. There is no wasted wording.

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?

The description covers the core invocation rules for a 7-parameter creation tool with annotations and no output schema. It does not mention permissions or the shape of the created result, but those are secondary for correct invocation.

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 100%, so the baseline would be 3, but the description adds meaning beyond the schema by stating that direction is auto-set for deposits and withdrawals. The movementDate constraint is repeated from the schema, but the auto-direction rule is useful additional semantics.

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 gives a specific verb and resource: "Record a manual cash movement," and names the three movement types. It is clearly distinguishable from cash_register_movements_list/update/delete, though it does not explicitly reference those siblings.

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?

It explains field-level rules for direction and movementDate, including when direction must be supplied. However, it does not explicitly say when to choose this create tool over cash_register_ledger, cash_register_balance, or update operations.

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