mf_expense_auth_callback

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

No annotations exist, so the description carries the full behavioral burden, yet it only says an access token is obtained. It omits whether the authorization code is single-use, whether the token is cached/persisted, what happens on an expired or reused code, and what the failure response looks like.

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 the action first and the usage condition in parentheses; nothing is wasted. It is terse to the point of under-specifying, but there is 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 a simple one-parameter token-exchange tool with no output schema, the description does state the return (access token) and the trigger condition (OOB mode). It leaves out the prerequisite chain (mf_expense_auth_start) and any error or token-lifetime behavior, so an agent would still need to infer how this fits into the auth sequence.

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% with a single required 'code' parameter that the schema already documents as '認可後に取得した認証コード'. The description's mention of 認証コード restates the schema without adding format, source, or expiration semantics, so baseline 3 applies.

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?

Description states a specific verb+resource pair (認証コードを使用してアクセストークンを取得します) scoped to the expense API, which correctly separates it from the sibling mf_auth_callback and mf_accounting_auth_callback that serve other APIs. It never explicitly names those siblings, so differentiation is implied by the 経費 prefix rather than stated.

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 parenthetical '(OOBモードで認証後に使用)' gives a clear usage condition: this is the step to call after an out-of-band authorization flow. No when-not guidance and no reference to the preceding mf_expense_auth_start / mf_expense_auth_status tools, so the workflow position is only partially pinned down.

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