storage_iscsi_enable

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

The description claims the tool is idempotent, but the annotations set idempotentHint to false, which is a direct contradiction. Although the description provides rich behavioral details, the contradiction violates the rule and forces 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 well-structured and every sentence adds value: purpose, context, idempotency, side effects, error handling, and parameter details. It is appropriately sized for the tool's complexity.

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?

The description covers prerequisites, behavior, output, and error remediation. It is complete for an agent to select and invoke the tool, though the annotation contradiction in idempotency is a trust issue.

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?

The schema has no property descriptions (0% coverage), but the description's 'Args' section thoroughly explains each parameter, including the exact format for host_name, the meaning of dry_run, and the optional target.

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 tool's function: 'Enable the software iSCSI adapter (vmhba) on an ESXi host.' It uses a specific verb and resource, and distinguishes itself from sibling tools by positioning as a prerequisite for storage_iscsi_add_target.

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?

Explicit guidance is provided: 'Required prerequisite before storage_iscsi_add_target' and 'Check current state first with storage_iscsi_status.' This tells the agent when to use the tool and suggests an alternative for checking state.

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