mf_accounting_auth_callback

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

No annotations are provided, so the description carries the full burden. It only states that it exchanges a code for a token and omits what happens on invalid/expired codes, token lifetime, or error behavior — significant gaps for an OAuth callback step.

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 no wasted words. Compact and clear, though the parenthetical could be integrated more cleanly.

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 single-parameter OAuth callback with no annotations and no output schema, the description covers the core action but lacks flow positioning (which sibling precedes/follows) and any error/token context an agent would need to call it confidently.

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 'code' parameter is already documented as the authorization code. The description restates this concept but adds no format, source, or validation detail beyond the schema, which matches the baseline.

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?

States a specific verb (取得する / obtain) and resource (アクセストークン / access token) driven by the authorization code. It is clear what the tool does, though it does not explicitly distinguish itself from siblings like mf_accounting_auth_start or mf_accounting_refresh_token by name.

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モードで認証後に使用)' signals when to use it — after authentication in OOB mode — which is useful implied sequencing. However, it names no explicit alternative or exclusion condition to distinguish it from the other auth-step siblings.

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