storage_iscsi_remove_target

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

Annotations already indicate destructiveHint=true. The description adds the rescan behavior, which is useful. However, it does not disclose reversibility, permission requirements, or effects on active connections.

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 reasonably concise with a title and an Args list. The Args list is somewhat redundant with the schema but adds descriptions, which justifies its length. No unnecessary verbosity.

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 an output schema exists (context shows 'Has output schema: true'), the description does not need to explain return values. It covers the main action and side effect (rescan), but could elaborate on error conditions or the rescan process.

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 description coverage is 0%, but the description's Args list provides meaningful descriptions for all four parameters (e.g., 'iSCSI target IP address', 'port default 3260'), adding value beyond the schema titles.

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 'Remove' and the resource 'iSCSI send target from an ESXi host', with explicit side effect 'rescan storage'. This distinguishes it from sibling tools like 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?

The description lacks explicit guidance on when to use or not use this tool. No prerequisites (e.g., target must exist) or alternatives are mentioned. Only the action is stated without usage context.

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