Initialize disk with GPT

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

Description reinforces the destructiveHint annotation with explicit 'DESTRUCTIVE — wipes existing data' and adds behavioral guidance to ask for confirmation. No contradictions with 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?

Two sentences, front-loaded with purpose, followed by critical warning. Every sentence earns its place with no fluff.

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?

Covers the essential aspects: what it does, that it's destructive, and the need for confirmation. Without an output schema, it misses details on return value, but for a destructive action these are the key points. Could mention irreversibility explicitly but 'wipes existing data' implies it.

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 only 50% schema description coverage, the description adds no parameter details, missing explanations for 'node' and 'uuid'. The schema descriptions for 'disk' and 'confirm' are present, but the description does not compensate for the gaps.

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?

Description clearly states the action: initialize a disk with a fresh GPT partition table. The verb 'Initialize' and resource 'disk with GPT' are specific, and the tool is easily distinguished from siblings like 'wipe_node_disk'.

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?

Explicitly warns about destructiveness and requires user confirmation, providing clear when-to-use context. However, it does not mention alternative tools for similar operations, such as 'wipe_node_disk'.

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