mfc_ca_postTransactionJournalize

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

With no annotations, the description carries the burden and it delivers: '帳簿書き込み。要ユーザー承認' signals a mutating ledger write requiring user approval, and the auto-completion note explains that several fields will be populated by MF. It stops short of describing approval mechanics, reversibility, or error responses, so it is not a 5.

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 one tight sentence plus two short clarifications, with the core purpose, the required input, and the auto-completion behavior all front-loaded. No filler or repetition.

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 an 11-parameter, approval-gated write tool with no output schema or annotations, the description gives essential starting points but omits the approval workflow, success/failure results, and guidance against sibling journal tools. It is adequate but not complete.

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 low (36%), and the description compensates partially by identifying account_id as the only user-supplied counterpart required and by grouping debit/credit direction, account-side subject, tax classification, and invoice_kind as automatically completed. It does not clarify memo, tags, remark, department_id, sub_account_id, or trade_partner_code.

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 states a specific action: '明細から仕訳を作成します' (creates journal entries from transaction details), with a clear resource and ledger-write scope. It does not explicitly name or differentiate from sibling tools like mfc_ca_postJournals, so it misses the highest tier.

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 context is implicitly clear: use this to journalize an existing transaction by providing account_id, with user approval required. However, it never tells the agent when to choose this over siblings such as mfc_ca_postJournals or mfc_ca_postTransactions, nor when not to use it.

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