zabbix_get_items

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

With no annotations provided, the description must disclose behavior on its own. It indicates a read-only 'Get' operation but does not mention important behavioral aspects such as pagination, result size limits, authentication requirements, or the structure of the returned data. It also fails to explain what happens when no filters are given (e.g., returns all items), which could be a significant omission for a 13-parameter tool.

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 an efficient single sentence with no fluff or redundancy. It front-loads the primary action and resource. While it is brief relative to the tool's complexity, brevity itself is a positive trait here; it doesn't repeat schema information, which aligns with conciseness. However, it could arguably be more informative without being verbose, so it doesn't merit a 5.

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?

Despite the rich schema, the description is the only source for contextual guidance. It lacks an explanation of what constitutes an 'item' in Zabbix, when to choose this over the many sibling tools (e.g., zabbix_get_latest_data, zabbix_get_triggers), and what the response format will look like (no output schema). For a complex tool with 13 parameters and nested objects, this is insufficient for an agent to confidently select and invoke it without additional context.

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 schema already documents all parameters (filter, search, output, hostids, etc.). The description adds minimal semantic value by mentioning 'filtering and output options', but this only vaguely maps to the existing parameter descriptions. Since the schema carries the full parameter burden, a baseline score of 3 is appropriate; the description doesn't disambiguate tricky choices like 'filter' vs 'search' or explain the effect of 'output'.

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 clearly states a specific verb and resource: 'Get items from Zabbix', which distinguishes it from sibling tools like zabbix_get_triggers or zabbix_get_hosts. It identifies the core action and target, though it lacks explicit scope details (e.g., that it returns item definitions, not values). The added 'with filtering and output options' hints at flexibility but doesn't fully differentiate from related item-value tools like zabbix_get_latest_data.

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 guidance is provided on when to use this tool versus alternatives. The description doesn't mention any exclusions or direct the user to tools like zabbix_get_latest_data for current values or zabbix_get_history for historical data. It simply states the function without contextual usage advice, leaving the agent to infer from the schema and sibling names.

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