erpnext_doc_submit

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

Annotations already declare destructive and non-read-only behavior, and the description adds concrete side-effect information: 'may post stock/accounting effects.' This goes beyond the annotations and helps the agent anticipate impact, though it does not cover dry_run behavior or reversibility.

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 two short sentences with no filler. The core action is front-loaded, and the sensitivity warning earns its place as important supplementary information.

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 mutating, destructive-capable tool, the description does not explain when submission is appropriate, what 'frozen' implies as a prerequisite, how dry_run changes behavior, or what the output represents. The presence of an output schema does not fill these gaps.

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%, and the description does not explain doctype, name, or dry_run. The dry_run parameter, which is essential for safe invocation, is completely undocumented in both the schema and the description.

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 identifies the operation as 'Submit' and the resource as 'a frozen current document through Frappe,' which distinguishes it from sibling create/update/cancel/delete operations. It does not explicitly contrast with sibling tools or explain 'frozen current' in depth, so it stops just short of full differentiation.

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 offers no guidance on when to use this tool versus alternatives, what conditions make a document ready to submit, or when dry_run should be used. The only additional note is a sensitivity warning about consequences, not selection criteria.

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