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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Same body and validation as POST /api/transactions', which is vague and assumes external API knowledge. It does not disclose that this is a mutating operation, that reference-data values may need to exist unless allow_new_values is set, or what side effects occur.

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 two sentences with no fluff. It front-loads the core purpose and then points to the API contract. Every sentence earns its place, and there is no redundant repetition of the tool name.

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 tool with 20 parameters, 12 required fields, no output schema, and no annotations, this description is insufficient. It relies on the agent already knowing POST /api/transactions, does not mention return behavior, and does not summarize required inputs. It is far from self-contained.

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 15%, so the description must compensate, but it does not explain the 20 parameters. The 'from-asset to to-asset' framing provides a useful high-level mapping for from_* and to_* fields, but leaves account, provider, ticker, amount, category, and risk semantics undocumented.

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 uses a specific verb and resource: 'Log a trade (buy / sell / swap)'. The 'from-asset to to-asset' phrasing clarifies the trade structure, and 'Same body and validation as POST /api/transactions' gives a precise contract. This clearly distinguishes it from siblings like record_balance_adjustment.

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 does not state when to use this tool versus alternatives, nor does it mention exclusions or prerequisites. While it implies usage for recording trades, it gives no guidance about using list_transactions for retrieval or record_balance_adjustment for non-trade changes.

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