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

With no annotations at all, the description carries the full behavioral burden, and it largely fails to. It signals this is a write with validation ('Same body and validation as POST /api/transactions') but discloses nothing about permissions, whether the trade is reversible/editable, side effects on balances or reference data, or the fact that new accounts/providers require an explicit opt-in flag.

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?

Two tight sentences with the core purpose front-loaded and no filler. It loses a point because the second sentence offloads meaning to an external API endpoint the agent may not know, rather than stating the constraint directly.

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 12-required-parameter write operation with no annotations, no output schema, and 19% schema coverage, this is far too thin. The description should at minimum explain the from/to ledger model, the currency-value field, and the new-reference-data opt-in, none of which it covers.

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 description coverage is only 19% across 21 parameters, so the description must compensate and it does not. The from-/to- framing hints at how the paired fields relate, but risk, category, description, ticker, account, and provider fields are left entirely unexplained, and there is no indication of which fields must agree or how amounts are validated.

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 ('Log') and resource ('trade'), and clarifies the operation's shape by naming the buy/sell/swap variants and the from-asset → to-asset model. It is readily distinguishable from read siblings like list_transactions or record_balance_adjustment, though it does not explicitly name those neighbors.

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?

There is no explicit when-to-use/when-not-to-use guidance. The reference to 'POST /api/transactions' is a backend implementation hint rather than a routing rule, and nothing tells the agent how this differs from sibling record_balance_adjustment, which is a plausible confusion point for balance-affecting writes.

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