item_create

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

Annotations already indicate this is a mutating, non-idempotent operation, and the description reinforces that by saying 'Create a new item.' It adds useful context about what items represent, but it does not disclose potential side effects, such as duplicate-key behavior or required host relationships, beyond what the schema already implies.

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 short and front-loaded with the primary action. The supporting sentences about item semantics are useful but somewhat generic; they could be tighter, yet they do not add significant bloat.

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 rich input schema and annotations, the description provides enough baseline context to understand the tool's purpose. However, it misses practical guidance such as when interfaceid is required or how this relates to host_create/host_get, so completeness is adequate but not strong.

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 100%, so the parameters are already well documented. The description offers a high-level conceptual mapping to the metric name, collection method, interval, and data type, but it does not add meaningful detail beyond the schema itself.

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 opens with 'Create a new item in Zabbix,' giving a specific verb and resource. It clearly differentiates this tool from the sibling item_get, item_update, and item_delete tools by establishing creation as the action.

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 explains what items are conceptually but does not state when to prefer item_create over the many related siblings. It provides no explicit when-to-use guidance, no alternatives, and no preconditions such as 'requires an existing host.'

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