erpnext_work_order_make_stock_entry

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

Annotations already indicate this is a non-read-only, destructive, non-idempotent operation, so the description does not need to restate that. The phrase 'freeze create/submit as one confirmable dependent batch' adds some behavioral context beyond the annotations by suggesting a batched, confirmable workflow. However, it remains vague about side effects, confirmation mechanics, and what 'freeze' actually means in practice.

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-loads the primary action with 'Generate Stock Entry using ERPNext.' It contains no filler or redundant restatement of the schema. However, the awkward and unclear 'freeze create/submit as one confirmable dependent batch' phrase reduces structural clarity even though it is concise.

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?

Given the tool's complexity—9 parameters, 0% schema coverage, and a destructive mutation—the description is far too sparse. It does not explain valid purpose values, the interaction between submit, save_draft, and dry_run, or how the 'dependent batch' is confirmed. The output schema exists, but it cannot compensate for missing workflow and parameter guidance.

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 0%, so the description carries the burden of explaining parameters, but it fails to do so. The only implicit parameter hint is 'create/submit,' which loosely maps to the submit boolean. Nothing explains purpose, qty, dry_run, save_draft, target_warehouse, source_stock_entry, or is_additional_transfer_entry, leaving the agent to guess critical input semantics.

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 action and resource: 'Generate Stock Entry using ERPNext.' This is clear and distinguishes the tool from generic document tools such as erpnext_doc_create. However, the phrase 'freeze create/submit as one confirmable dependent batch' is cryptic and does not clearly explain the core behavior, and no explicit differentiation from sibling tools is provided.

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 on when to use this tool versus alternatives like erpnext_doc_create, erpnext_doc_submit, or erpnext_batch_prepare. There is no mention of prerequisites, exclusions, or conditions that would select this tool over its siblings. The intended use is only implied by the tool name and the phrase 'Work Order,' not stated in the description.

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