record_transaction

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

Without annotations, the description discloses the default inventory adjustment and confirms it is a real write. However, it lacks detail on authentication requirements beyond the key, idempotency, or error behavior.

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 concise at three sentences, with the purpose front-loaded. Every sentence adds value, though the requirement line could be better integrated.

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 10 parameters, no output schema, and no explanation of return values or error handling, the description is incomplete for a write operation. It should mention what the response contains or how to confirm success.

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?

With only 50% schema coverage, the description adds minimal meaning beyond the schema. It mentions BUY/SELL types implicitly but does not explain parameters like fees, notes, source, or skipInventorySync in context.

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 tool records buy/sell transactions, specifies the resources (transaction) and verb (record), and distinguishes from sibling tools like delete_transaction or list_transactions.

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 mentions a required API key but does not provide guidance on when to use this tool versus alternatives like add_buy_list or import_buy_list. No explicit usage context or exclusions.

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