mf_accounting_get_journal

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it discloses almost nothing. '取得する' implies a read with no side effects, but there is no statement about authentication requirements, what happens for a nonexistent ID, or the shape of the response.

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?

A single, front-loaded sentence with zero padding or redundancy. It is efficient, though arguably under-specified rather than optimally concise.

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 one-parameter read operation with no output schema, the definition is minimally viable: an agent can call it correctly from the name and schema alone. It nonetheless omits return-shape expectations and sibling routing that would make it fully 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 description coverage is 100% and the single parameter journal_id is already documented in the schema as '仕訳ID'. The description adds no format, source, or constraint detail beyond that, so the baseline 3 applies for schema doing the heavy lifting.

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 verb (取得する = retrieve) and resource (会計仕訳 = accounting journal), so the agent knows it fetches journal entry details. However, it does not differentiate itself from its obvious sibling mf_accounting_list_journals, nor does it make explicit that it returns a single record keyed by ID.

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 when-to-use guidance at all: no mention of using this over mf_accounting_list_journals for enumeration, no prerequisites, and no error/not-found conditions. The agent must infer usage purely from the name.

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