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

Richly discloses behavior beyond annotations: journal entries are opaque and wallet-scoped, P&L attribution is later applied from on-chain fills, idempotency_key makes replays safe, unknown tx_signature returns 404, and omitted tx_signature auto-links the wallet's most recent confirmed transaction as best-effort fallback. No contradiction with readOnlyHint=false, idempotentHint=true, or destructiveHint=false.

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 long, but it is front-loaded and every paragraph earns its place given the zero-coverage schema and 14 parameters. It loses one point for some explanatory asides (Layer 2 firewall proof, repeated emphasis on explicitness) that could be tightened.

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?

With an output schema present and annotations covering safety/idempotency, the description covers all operationally important context: privacy, idempotent replay, evidence linking, tx_signature fallback semantics, and workflow ordering. An agent has enough to call this correctly without external knowledge.

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?

Despite 0% schema description coverage, the description adds real meaning for the core params: rationale, intended_action, expectations, idempotency_key, tx_signature, signal_ids, suggestion_id, strategy_id, and wallet scope. However, it leaves required decision_type and several optional metadata fields (asset, caller_id, session_id, client_platform) unexplained, so it doesn't fully compensate for the empty schema descriptions.

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?

Opens with a specific verb+resource: 'Record a decision in your private, wallet-scoped journal (free write).' It clearly distinguishes itself from read-side siblings by naming journal_query and get_my_performance as the query-back tools.

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?

Provides an explicit workflow: 'journal before (or as) you act; query it back with journal_query / get_my_performance.' It also tells the agent that autonomous strategy executions are already journaled automatically, so this tool is for adding the agent-authored layer, and explains when to attach tx_signature.

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