zabbix_item_update

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

The description does not disclose any behavioral traits. With no annotations present, the description fails to inform about mutability, idempotency, side effects (e.g., cascading updates, validation), authentication needs, or error behavior. The agent is left blind to how invoking this tool affects the system.

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 a single sentence, which is concise but fails to front-load essential information. It prioritizes a technical reference ('Zabbix API item.update method') over actionable guidance. At minimum, it should state the tool's purpose in plain language and hint at parameters.

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 extensive list of sibling tools (over 200), this description is grossly incomplete. It does not explain how item.update differs from item.create, item.get, itemprototype.update, or other related tools. There is no mention of output schema, even though one exists. The agent lacks sufficient context to use the tool reliably.

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 input schema has a single 'params' object with no documented properties and 0% schema description coverage. The description does not clarify the structure or required fields of 'params', such as item ID, fields to update, or syntax examples. Without additional guidance, the agent cannot construct valid input.

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 'Zabbix API item.update method' merely restates the tool name and references the API method. It lacks specificity about what 'update item' entails (e.g., modifying item properties, updating configuration) and does not differentiate from related tools like zabbix_item_create or zabbix_item_get. A knowledgeable user might infer the purpose, but the description provides minimal clarity.

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?

No usage guidelines are provided. The description does not indicate when to use this tool versus alternatives (e.g., zabbix_item_create for creation, zabbix_item_update for modification), nor does it mention required parameters, prerequisites, or typical scenarios. This leaves the agent with no context for appropriate invocation.

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