zabbix_monitoring

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

Annotations already flag destructive=true and non-idempotent; the description adds useful beyond-schema behavior: reads return compact defaults and writes require a two-step preview/confirm_token flow. It still does not explain permission requirements or the concrete impact of destructive methods such as delete/clear.

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 method enumeration is dense but earns its space by conveying the tool's broad scope, and the important write workflow is stated compactly. The description is front-loaded with the API identity and method list, though the long semicolon list is harder to scan.

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 API dispatcher with no output schema, the description covers supported method families, compact read defaults, the two-step write protocol, and a docs alternative. It is not fully complete because it omits sibling-tool routing and does not mention host-oriented methods even though host.get appears in the schema example.

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 coverage is 100%, so method, params, and confirm_token are already documented in structured fields. The description reinforces the confirm_token write flow but adds no new syntax or constraints beyond the schema.

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 as the Zabbix monitoring API and enumerates the method families it supports, so an agent knows this is a generic method dispatcher rather than a single-operation tool. It does not distinguish the tool from siblings such as zabbix_raw_api or the many specialized Zabbix 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?

It supplies procedural guidance for writes (preview then repeat with confirm_token) and directs agents to zabbix_describe_method for documentation. However, it never states when to choose this generic dispatcher over specialized siblings like get_active_problems or zabbix_hosts, nor when not to use it.

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