erpnext_batch_prepare_from_artifact

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

Annotations indicate destructiveHint=true, readOnlyHint=false, and idempotentHint=false, yet the description gives no hint of side effects, destructive behavior, or non-idempotence. The word 'prepare' suggests a benign read-like operation, which is potentially misleading given the destructive flag, but it does not directly contradict the annotations.

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 a single, front-loaded sentence with no filler or redundancy. It communicates the core operation efficiently, which is appropriate for its short length.

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?

With three parameters, no schema property descriptions, and a destructive annotation, the description is too thin to fully support correct invocation. It gives no parameter semantics, no side-effect warning, and no routing guidance, though the presence of an output schema partially reduces the need to document return values.

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 artifact_id, expected_count, and label. It only hints that artifact_id refers to the source artifact and that the output is a JSON array of requests, but it does not explain expected_count or label, leaving key parameters 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?

States a specific verb ('prepare') and resource ('a complete JSON array of requests') from a 'finalized source artifact', which gives the agent a clear picture of the operation. It does not explicitly differentiate from sibling erpnext_batch_prepare, but the artifact-based source is a distinguishing clue.

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 phrase 'from a finalized source artifact' implies that the tool should be used only after an artifact has been finalized, providing some contextual guidance. However, it does not explicitly state when to use this tool versus alternatives like erpnext_batch_prepare, nor does it mention any exclusions or prerequisites beyond finalization.

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