zabbix_create_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that a new item is created, but does not disclose side effects, required permissions, idempotency, or what happens if the item key already exists. The absence of return-value information and error conditions makes behavioral transparency weak.

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, front-loaded sentence with zero wasted words. It communicates the core purpose efficiently, matching the high-conciseness standard of exemplary descriptions. No unnecessary details or repetition.

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 tool with 14 parameters, no output schema, and no annotations, a one-sentence description is insufficient. It does not explain expected return values, prerequisites (e.g., host must exist), or behavior on validation failures. The description is minimal and leaves critical context unaddressed.

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 provides descriptions for all 14 parameters with 100% coverage, so the schema does the heavy lifting. The description adds no additional parameter semantics beyond 'Create a new item', which is simply the tool's action. Baseline score of 3 is appropriate.

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 'Create a new item in Zabbix' clearly states a specific action (create) and resource (item), distinguishing it from sibling tools like zabbix_update_item, zabbix_delete_items, and zabbix_get_items. However, it lacks additional context about what an item is or the scope of creation, so it does not fully differentiate from other create tools.

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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or contrast with sibling tools like zabbix_create_trigger or zabbix_create_host. Agents are left to infer appropriate usage solely from the tool name and sibling list.

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