pve_node_disk_initgpt

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

Discloses mutation risk, irreversible action, and need for confirmation. Also notes the endpoint is not live-verified. With no annotations, this provides good behavioral insight.

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?

Concise and front-loaded with purpose and risk. The endpoint line is slightly redundant but not harmful. No unnecessary words.

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 operational behavior and risk, but lacks output description and parameter details. For a mutation tool with an output schema, return values are not mentioned.

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?

Only the confirm parameter is explained indirectly; other parameters (disk, node, proximo_target) lack any description. Schema coverage is 25%, so description should compensate but does not.

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 the verb 'initialize' and the resource 'GPT partition table on a node disk', distinguishing it from sibling disk operations like wipe or list.

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?

Provides clear risk warnings and requirement for confirm=True, but does not explicitly compare with alternative disk tools or specify when not to use.

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