record_transaction

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

Without annotations, the description discloses key traits: it is a real write, requires authentication, and adjusts inventory by default. It also hints at the skipInventorySync parameter. However, it does not cover idempotency, rollback, or side effects beyond inventory.

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 succinct with two sentences, front-loading the main purpose. It is efficient but lacks some details that could be included without bloat, such as notes on required parameters.

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 (10 params, write operation, no annotations or output schema), the description is incomplete. It omits return value, error behavior, and parameter constraints beyond what the schema provides, leaving gaps for an AI agent.

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 only 50%, so the description must compensate. It adds meaning for 'type' (BUY adds, SELL subtracts) and 'skipInventorySync' (default false updates inventory), but many parameters like quantity, fees, and notes remain unelaborated. Partial addition of value.

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 'Record' and the resource 'transaction', and distinguishes between buy/sell types. It explicitly mentions inventory adjustment, setting it apart from other transaction tools like delete_transaction or update_transaction.

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 explains the default behavior (inventory adjustment) and indicates it's a real write requiring an API key, but does not compare this tool to alternatives like add_inventory or update_inventory for inventory-specific tasks. No explicit 'when to use' vs siblings.

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