erpnext_doc_create

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

Annotations already signal that the operation mutates state (readOnlyHint=false, destructiveHint=true). The description adds some behavioral context by mentioning 'safe_mode preflights' and 'expected_lengths checks child rows', which are useful, though safe_mode is unexplained and not present in the input schema.

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 compact: two short sentences, with the primary purpose front-loaded. It avoids bloat, though 'safe_mode preflights' is cryptic and could use a brief clarification without hurting conciseness much.

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 create operation with a required free-form doc object, the absence of guidance on document shape, dry_run behavior, safe_mode semantics, and relationship to sibling tools leaves significant gaps. The output schema helps with return values but cannot compensate for missing parameter and usage context.

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?

With 0% schema description coverage, the description must carry parameter meaning, but it only adds context for expected_lengths ('checks child rows'). The required doc parameter and dry_run are left undocumented, and the mention of safe_mode refers to a concept outside the schema, so parameters remain largely underspecified.

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 clear verb and resource: 'Create a document' using native REST. This distinguishes it from sibling tools like erpnext_doc_update/delete/list/get by the core create action, but it does not explicitly define the scope of 'document' or name an alternative, so it stops 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?

There is no guidance about when to choose this tool over alternatives such as erpnext_doc_update, erpnext_call_method, or erpnext_api_request. 'Using native REST' hints at an implementation approach but is not an explicit usage condition or exclusion, leaving the agent to infer selection criteria.

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