erpnext_naming_series_configure

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

Annotations already communicate readOnlyHint=false and destructiveHint=true, so the mutation risk is covered. The description adds some useful context by describing the operation as being 'frozen' into a 'sensitive plan' and noting that no separate whitelist is used. However, it does not explain concrete side effects, what makes the plan sensitive, or what openWorldHint=true implies behaviorally.

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 contains no filler, so it is concise in length. But the single dense sentence is not structured for comprehension, and the semicolon-separated 'no separate whitelist' clause is left unexplained. It is under-specified rather than effectively 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 a four-parameter configuration tool with two required fields and a rich ecosystem of plan-related siblings, the description leaves too much unexplained: what a naming-series controller request is, what a sensitive plan means, and how this tool connects to plan execution or validation. The output schema mitigates return-value uncertainty, but the description still fails to provide enough operational context for correct invocation.

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 mention doctype, series_options, dry_run, or counters at all. The description had the responsibility to compensate for the bare schema but provides no help on valid values, required combinations, or how dry_run alters behavior. This is a critical gap for a tool with four parameters.

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 names a specific action ('Freeze') and resource ('native naming-series controller requests'), and the 'no separate whitelist' clause hints at a distinctive approach. However, the meaning of 'freeze ... as one sensitive plan' is opaque domain jargon, and the description does not clearly explain what the tool actually configures or accomplishes. It is not a tautology, but it is only a vague statement of purpose.

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 explicit guidance about when to use this tool versus any of the many siblings such as erpnext_plan_execute, erpnext_batch_prepare, or erpnext_doc_update. The phrase 'no separate whitelist' implies a contrast with an alternative approach, but it does not name a sibling or specify a condition. An agent is left to infer the intended use.

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