erpnext_input_finalize

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to restate basic safety. It adds useful context about verification and the finalization gate for execution/upload, but it does not disclose that finalization may be irreversible or that the input may become locked after this step.

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?

Two sentences with no filler, and the key behavioral consequence is stated early. The structure is efficient, though it sacrifices parameter-level detail that would be more valuable than brevity.

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 single-parameter tool with an output schema and annotations, the description covers the main purpose and consequence. However, it omits the meaning of artifact_id and does not explicitly place this step in the sequence between appending input data and executing/uploading.

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 the meaning or role of artifact_id at all. Since this is the only parameter and is required, the agent must infer what artifact_id refers to, which is a significant gap.

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: verifying source length and SHA-256 and marking an input as finalized, with the outcome that only finalized inputs can be executed/uploaded. It clearly differentiates this tool from input_begin and input_append by focusing on the finalization step. It could be slightly stronger by explicitly naming the finalize action rather than leading with 'Verify'.

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 'Only finalized inputs can be executed/uploaded' implies this should be used after input construction and before execution/upload, but it does not explicitly name sibling tools or state when not to use it. The guidance is present but indirect and could mislead an agent into thinking this is a read-only verification step.

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