storage_iscsi_add_target

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

Annotations already indicate a write operation (readOnlyHint=false), but the description adds valuable context about the rescan side-effect. There is no contradiction; the description complements the annotations.

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 concise and front-loaded with the purpose. It uses an Args list for structure without redundancy. Every sentence serves a purpose, though the Args list could be slightly more integrated.

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 the complexity (add target to ESXi host, rescan, 4 params, output schema exists), the description is incomplete. It omits prerequisites (e.g., iSCSI enabled), behavior on duplicate targets, and return value details. With 0% schema coverage, more context is needed.

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?

With 0% schema description coverage, the description only lists parameter names with minimal explanation. For example, 'target' is described as 'Optional vCenter/ESXi target name from config', but other parameters like 'host_name' and 'address' just repeat the name. This does not significantly add meaning beyond the schema.

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 it adds an iSCSI send target to an ESXi host and rescans storage, using a specific verb and resource. It effectively distinguishes from sibling tools like storage_iscsi_remove_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 indicates what the tool does but does not explicitly state when to use it versus alternatives or provide exclusion criteria. Implicitly, it is for adding targets, but lacks explicit guidance.

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