termix_add_many_hosts

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

With no annotations, the description carries the behavioral burden and discloses two important traits: a required confirm=true flag and per-item result reporting so one failed row does not abort the batch. It does not cover auth requirements, rate limits, or idempotency, but it handles the key mutation and partial-failure semantics.

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 four compact sentences and front-loads the core purpose. Every sentence adds relevant information: batch semantics, item format reference, confirmation requirement, and error handling.

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 tool has an output schema, return values need not be explained. The description covers the mutation confirmation and partial-failure behavior, but because the input schema provides no field descriptions and the description defers host object details to a sibling command, it is slightly incomplete for an agent unfamiliar with termix_hosts add.

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%, so the description must compensate. It adds useful meaning for both parameters by requiring confirm=true and by saying each hosts item matches the data passed to termix_hosts add, but it does not document the actual host object fields, leaving a gap at 0% coverage.

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 states a specific verb and resource: adding several hosts in one batch. It also distinguishes itself from the sibling tool termix_hosts add by explaining that each item uses the same data shape as the single-add command.

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?

It gives clear context for when to use this tool: when adding several hosts at once, with the item format matching termix_hosts add. It also states the confirm=true prerequisite, though it does not explicitly say when not to use it or name alternatives for single-host additions.

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