initialize_gpt

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

With no annotations, the description carries full burden. It explicitly warns 'WARNING: destroys all data', which is the key behavioral trait. No other behaviors disclosed, but for a simple initialization, this is sufficient.

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 extremely concise: one sentence plus a two-line parameter list. No unnecessary words; every sentence is essential.

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 the tool's simplicity, 2 required parameters, and an existing output schema, the description covers purpose, parameters, and a critical warning. No gaps for an initialization 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 0%, so description must add value. It explains 'node' as 'The node name' and 'disk' with an example '/dev/sdb', adding meaning beyond parameter names. Could provide more constraints like format or validation.

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 clearly states 'Initialize a disk with GPT partition table', using a specific verb and resource. It distinguishes itself from sibling tools as the only one for initializing a disk partition table.

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?

Includes a warning about data destruction, which implies when to use (when data can be lost) and when not to. However, it does not explicitly mention alternatives or conditions for use compared to other disk-related tools.

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