m3_create_cash_desk_document

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does mention 'Async import queue,' implying the creation is queued rather than immediately completed, but it does not explain side effects, validation, failure behavior, or what the agent should expect after invocation. The async hint is useful but underdeveloped.

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 short and front-loaded with the core operation. It does not waste words, though the two appended notes are dense and would benefit from more precise phrasing.

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 10-parameter creation tool with no annotations and no output schema, the description is too thin. It omits important context such as whether isExpense defaults to income, how the async import queue affects confirmation or response, and what 'controlling variables' means in practice.

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 80%, so most parameters are already documented in the schema. The description adds no concrete parameter-level meaning; 'controlling variables' is only a vague hint and does not clarify documentNumber, variableSymbol, or how controlling variables map to the schema.

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 clearly states the verb ('Create') and resource ('cash desk (register) document'), which distinguishes it from other m3_create_* siblings. The phrase 'Supports controlling variables' is vague and does not clarify what that capability entails.

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 description gives no guidance about when to use this tool versus alternatives like m3_create_bank_document, m3_create_stock_document, or m3_create_internal_document. There are no stated prerequisites, exclusions, or conditions that would lead an agent to prefer this tool.

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