mf_accounting_auth_status

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: it does not state that this is a read-only probe, whether it requires an existing token, whether it triggers any network call to the accounting provider, or what the returned status means (authenticated vs. token expired vs. not configured).

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 short sentence with the purpose front-loaded and no filler. It is efficiently sized, though its brevity borders on under-specification rather than true conciseness.

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 zero-parameter tool in a crowded auth toolset with no annotations and no output schema, the description should at minimum explain what the status result tells the caller and how it fits the auth flow. None of that is present, so an agent cannot act on the result 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?

The tool takes zero parameters, so per the rubric the baseline is 4. There is no parameter semantics to add, and the description correctly does not invent any.

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 names a specific verb and resource ('認証状態を確認する' / check auth status) and the mf_accounting_ prefix scopes it to the accounting API, which distinguishes it from the sibling mf_auth_status. It stops short of clarifying its relationship to mf_accounting_auth_start, mf_accounting_auth_callback, and mf_accounting_refresh_token, so sibling differentiation is only implicit.

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 guidance on when to call this versus the other auth-family tools. An agent facing mf_accounting_auth_start, mf_accounting_auth_callback, mf_accounting_refresh_token, and this tool gets no stated ordering, prerequisites, or exclusion conditions.

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