hpc_write_file

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the overwrite behavior is partially covered by structured data. The description does add real value by disclosing that it overwrites and that parent directories are created automatically, but the '(none configured)' note is ambiguous about whether the tool can actually run.

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 short sentences are efficient and front-load the core action. However the '(none configured)' parenthetical is confusing clutter that consumes space without earning it.

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 destructive write tool with no output schema, it conveys the key mechanics (overwrite, parent dir creation) but says nothing about permissions, size limits, or what happens on failure. It is adequate but leaves meaningful gaps for a mutation tool.

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 coverage is only 50% — path is documented as an absolute cluster path, but content has no description anywhere. The description adds no format, encoding, or size semantics for content, so it fails to compensate for the coverage 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?

States a specific verb and resource — create or overwrite a file — which is clear enough to distinguish it from read-side siblings like hpc_read_file. However it does not differentiate itself from the close sibling hpc_edit_file, and the parenthetical '(none configured)' muddies rather than clarifies the 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 when-to-use guidance and no mention of the obvious alternative hpc_edit_file for modifying existing content. The agent is left to infer the choice between creating/overwriting versus editing.

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