hosts_bulk_update

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation/safety profile is covered. The description adds the genuine bulk trait that the fields are applied to every host in `uuids`, but says nothing about partial-failure handling, reversibility, or whether fields merge vs. replace — relevant for a bulk mutation with no output schema.

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?

A single tight sentence with the scope constraint front-loaded and zero filler. It is efficient, though arguably under-sized for a 32-parameter bulk mutation.

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?

For a complex bulk mutation with 32 parameters, 3% schema coverage, no output schema, and no annotations describing outcomes, the description is too thin. It leaves the bulk semantics (per-host application, failure behavior, field semantics) largely to inference.

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 only 3% across 32 parameters, so the schema does essentially no work and the description carries the full burden. Pointing to hosts_update for the field semantics is a clever compensation, but it only names `uuids` and gives no syntax or detail for the 31 other parameters.

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?

States a specific verb (Update), resource (hosts), and scope (many at once), and explicitly ties the field semantics to the sibling hosts_update. An agent can distinguish it from the singular hosts_update and from other bulk host operations like hosts_bulk_enable/delete.

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?

Usage is implied: 'many hosts at once' signals this is the bulk counterpart to hosts_update, and 'same as hosts_update' anchors which fields apply. However, it never states when to prefer this over hosts_update, nor any exclusions or preconditions for the bulk path.

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