zabbix_config

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

Annotations already flag destructiveHint=true, readOnlyHint=false and non-idempotent, so the safety profile is known. The description adds behavior the annotations cannot convey: reads return compact defaults, and writes are two-step with a preview followed by a repeat call carrying confirm_token — important procedural context for a destructive dispatcher.

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 two-step write explanation is front-loaded and earns its place, but the long semicolon-separated method inventory consumes most of the text and overlaps heavily with what zabbix_search_methods and zabbix_describe_method exist to provide. It reads as a data dump rather than prioritised guidance.

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 generic dispatcher with no output schema, the description covers what an agent most needs (available methods and the confirm_token write protocol). It is still thin on what 'compact defaults' means in practice and how to obtain full read output, which matters for an open-ended config API.

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 method, params and confirm_token are already documented in the schema, and the baseline of 3 applies. The description contributes the fact that confirm_token originates from the preview call and that params accepts an array of ids for deletes, but that detail is largely duplicated by the schema text.

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 names the resource domain (Zabbix configuration API) and enumerates the concrete method families it dispatches (itemprototype, triggerprototype, discoveryrule, httptest, usermacro, valuemap, regexp, correlation, configuration). An agent can tell this is a generic config-domain dispatcher, but the description never contrasts it with the sibling zabbix_raw_api, so the boundary between the two is left for the agent to infer.

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?

It gives one explicit routing instruction (use zabbix_describe_method for docs and parameters) and explains the two-step write flow, which is real usage guidance. However, it never says when to choose this tool over zabbix_raw_api or the curated domain siblings like zabbix_hosts, and gives no prerequisites or exclusions.

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