storage_iscsi_enable

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

Annotations declare idempotentHint=false, but the description claims 'Idempotent: if the adapter is already enabled... without making changes.' This directly contradicts the annotations, which is a serious inconsistency. Per the rubric, a description contradicting annotations must receive a score of 1.

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 front-loaded with [WRITE] and the action verb, and nearly every sentence carries useful operational information: prerequisites, state-checking, effects, audit logging, and error behavior. It is reasonably sized, though the misleading idempotency assertion slightly undermines the trustworthiness of an otherwise tight definition.

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 prerequisites, side effects, non-disruptiveness, audit trail, the recommended status check, and return/error behavior; an output schema exists, so exact return details are not required. However, the contradictory idempotency statement means the behavioral contract is not fully reliable, so it is not a perfect score.

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?

Input schema description coverage is 100%, so the schema already documents host_name, target, and dry_run. The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 applies.

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 ('Enable'), a specific resource ('software iSCSI adapter (vmhba)'), and a clear host context ('on an ESXi host'). The [WRITE] prefix also immediately classifies the operation and distinguishes it from sibling inspect/status tools.

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 says this is a 'Required prerequisite before storage_iscsi_add_target' and tells the agent to 'Check current state first with storage_iscsi_status.' This gives clear sequencing and names the relevant sibling tools, so an agent knows when to use this tool versus alternatives.

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