record_cash_sale

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

With no annotations present, the description carries the full burden of behavioral disclosure. It only states that it records a transaction, without mentioning side effects, required permissions, tax calculations, or whether a ledger entry is created. This minimal disclosure leaves significant behavioral ambiguity.

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 well-structured, with a one-sentence purpose statement followed by a clean Args list. Every line is informative, with no redundant text or filler.

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 tool with 5 parameters and no output schema, the description is adequate for basic invocation. However, it lacks usage context, such as typical scenarios or relationship to accounting workflow, and doesn't explain return values or error conditions. It is minimally complete but not rich.

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 provides no parameter descriptions (0% coverage), but the description compensates by listing each argument with meaning: amount is 'excluding tax', tax_code has a default, and entity_name is described. This adds value beyond the schema's bare property names.

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 'Records a cash sale transaction' with a specific verb and resource. The term 'cash sale' distinguishes it from sibling tools like record_cash_purchase, record_client_invoice, and record_supplier_bill, making its purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios, prerequisites, or edge cases (e.g., when to use a cash sale instead of an invoice). Sibling names imply differences, but the description itself offers no explicit usage direction.

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