storage_iscsi_enable

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

The description adds the '[WRITE]' hint, which is consistent with readOnlyHint=false, but lacks details on side effects (e.g., disruption, reboot needs) or permissions required. Annotations already imply it's a write operation, so the description adds minimal extra behavioral context.

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 very short yet includes a purpose header and parameter definitions. It is front-loaded and concise, though could be slightly more structured.

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?

Output schema exists, so return values are documented externally, but the description omits input validation, idempotency (false), error conditions, and impact on existing iSCSI sessions, which are critical for a write operation.

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 the description must explain parameters. It defines 'host_name' as ESXi host name and 'target' as optional vCenter/ESXi target name, adding meaning beyond the schema types, though 'target' could be clearer.

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 'Enable' and the resource 'software iSCSI adapter on an ESXi host,' distinguishing it from sibling tools like storage_iscsi_add_target which manage targets.

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?

The description provides argument explanations but no guidance on when to use this tool vs alternatives, prerequisites, or conditions to avoid (e.g., if the adapter is already enabled).

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