mf_create_billing

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

No annotations are provided, so the description carries the full behavioral burden. Beyond 'creates an invoice', it reveals nothing about required authorization, whether creation is idempotent, what happens on missing required fields, or what the response contains (e.g., created ID). For a 9-parameter mutation tool this is minimal disclosure.

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?

It is a single, front-loaded sentence with no filler, which is structurally clean. However, it is so terse that it omits useful context that could have been included at little cost, so it is efficient but under-specified rather than genuinely well-crafted.

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 mutation tool with 9 parameters, 3 required fields, no output schema, and no annotations, the description is far too thin. It does not explain the creation flow, required minimum inputs, or the relationship to sibling tools like mf_create_billing_from_quote, leaving significant gaps for the agent.

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%, so every parameter (partner_id, billing_date, items, department_id, etc.) is already documented in the schema, including enum values for excise and date formats. The description adds no parameter-level meaning beyond what the schema supplies, so the baseline of 3 is appropriate.

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 (作成します = creates) and resource (請求書 = invoice/billing), plus a qualifier (インボイス制度対応 = qualified-invoice-system compliant). It is clear what the tool does, but it does not differentiate itself from the closely named sibling mf_create_billing_from_quote, so an agent cannot tell from the description alone which creation path to choose.

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, no prerequisites, and no mention of alternatives such as mf_create_billing_from_quote or mf_update_billing. The description states only the outcome, leaving the agent to infer when this tool is appropriate.

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