m3_create_bank_document

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

With no annotations, the description carries the full behavioral disclosure burden. It does reveal that the operation uses an async import queue and supports controlling variables, but it omits side effects, success/failure behavior, return values, and other consequences of creating a document.

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?

The description is very short and front-loaded with the core action. However, phrases like 'Supports controlling variables' and 'Async import queue' are cryptic and would carry more value if expanded slightly.

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 14-parameter creation tool with no annotations and no output schema, this description is too sparse. It lacks information about required setup, how the async queue processes requests, what response or confirmation the agent can expect, and how to handle errors or partial failures.

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 71%, so the schema already handles most parameters, but the description adds little beyond the vague phrase 'controlling variables.' It does not clarify the remaining undocumented parameters like constantSymbol, variableSymbol, specificSymbol, or documentNumber.

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 ('Create') and a specific resource ('bank document (payment)'), and clarifies the document subtype as a payment. This distinguishes it from sibling tools like m3_create_cash_desk_document, m3_create_issued_invoice, and m3_delete_bank_document.

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?

No guidance is given about when to choose this tool over alternatives such as m3_create_cash_desk_document or m3_create_issued_invoice. The purpose implies bank payment creation, but there is no explicit context, prerequisites, or exclusions.

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